Unique-Divine/jiyuu / ai-skills/gh-rev
gh-rev
VerifiedUse the gh-rev CLI to maintain a persistent Markdown review ledger for local branches and pull requests. Trigger when the user names gh-rev, asks to save or submit a durable review, inspect or implement existing findings, continue an independent review pass, or adopt branch history into a PR. Use the gh-pr-review skill for review content and judgment. Do not use this skill for a one-off review without a durable ledger.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.0 KB |
| references/cli.md | markdown | 3.8 KB |
| references/implement-review-feedback.md | markdown | 6.3 KB |
| references/review-local-branch.md | markdown | 2.4 KB |
| references/review-pull-request.md | markdown | 2.8 KB |
| references/work-revisions.md | markdown | 3.0 KB |
references/review-local-branch.md
View on GitHub# Review a local branch
Use this workflow when the review target is an exact local branch, whether or
not a pull request exists yet.
## Example: draft branch without a PR
For a request such as "Use gh-rev to review my `feature/cache` worktree":
1. Identify the checkout, repository slug (`owner__repo`), branch, and intended
base from Git and the user's context. Do not assume `main` if repository
instructions or branch metadata establish another base.
2. Use the intended worktree as the command directory, or select it with
`gh-rev -C /absolute/path/to/checkout`. The CLI discovers the repository;
explicit registration is available for migration or offline workflows.
3. Resolve the review range and ledger with explicit local authority:
```bash
gh-rev open owner__repo --branch feature/cache --base main --head local
```
4. Read the returned `context_path` and every prior review. Read the linked
issue or durable design notes before judging whether the implementation
matches its intent.
5. Use the `gh-pr-review` skill to review the exact `base_sha...head_sha`
reported by the CLI, including surrounding code and focused tests. Do not
review an ambient worktree `HEAD` when it differs from the named branch.
6. When the findings are final, allocate the matching revision:
```bash
gh-rev next owner__repo --branch feature/cache --head local --label initial
```
7. Fill the returned `review_path`. Remove the placeholder finding, write each
real finding with the exact marker described in `SKILL.md`, and include the
recommendation from the `gh-pr-review` skill.
8. Verify the artifact and scanner result:
```bash
gh-rev status owner__repo --branch feature/cache
gh-rev status todo owner__repo --branch feature/cache
```
If `next` refuses because the base or head moved after `open`, do not force the
old analysis into a new snapshot. Re-open the branch, inspect the new diff, and
adjust the review before allocating.
## Example: local work beyond a published PR
When a branch has a PR but the user specifically wants unpublished local work
reviewed, use branch mode and explicit local authority. Mention the divergence
in `## Scope`. Use PR mode instead if the user wants the code currently visible
to GitHub reviewers.
Do not create a PR merely to use the ledger. Branch histories are intentionally
useful for draft and private work and can be adopted by `gh-rev sync` later.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |