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-pull-request.md
View on GitHub# Review a pull request
Use this workflow for the PR state published on GitHub. A source checkout is
helpful for deep inspection and tests, but it is not a prerequisite for reading
the PR or producing a review.
## Example: online PR
For a request such as "Review PR #1153 with gh-rev":
1. Resolve the repository, PR number, issue, PR description, prior GitHub
comments, base/head refs, and immutable base/head SHAs with `gh`.
2. Inspect the installed CLI as described in [cli.md](cli.md).
3. Use a suitable repository checkout, discovered from the command directory
or selected with `-C`, and open the PR ledger:
```bash
gh-rev open owner__repo --pr 1153
```
Read the returned context and all prior revisions. Opening the PR may adopt
branch history into its canonical ledger; do not duplicate adopted reviews.
Use `sync` for bulk reconciliation or interrupted-adoption recovery, not as
a prerequisite for each review.
4. Use the `gh-pr-review` skill to review the GitHub PR head against its GitHub
base. Use `gh pr diff`, surrounding source from GitHub, and available
repository context. Materialize or update a local checkout when tests,
generated files, cross-file searches, or implementation work make that
useful.
5. Confirm the `gh-rev open` head SHA matches the PR head reviewed. Then
allocate and fill the revision:
```bash
gh-rev next owner__repo --pr 1153 --label independent
```
6. Verify the PR ledger:
```bash
gh-rev status owner__repo --pr 1153
gh-rev status todo owner__repo --pr 1153
```
PR mode uses the GitHub PR head as authority. Do not use `--head local` with
`--pr`, and do not silently review extra local commits.
## Local branch prerequisite
The current PR adoption model requires an exact local branch matching the
GitHub head branch, even though the GitHub PR head SHA remains authoritative
for the review. In that case:
- Still complete the requested online review from immutable GitHub base/head
evidence; lack of a source checkout is not a reason to skip review.
- If a matching local checkout already exists, use it only after confirming its
exact branch SHA matches the GitHub PR head.
- If the user also asks for implementation or local verification, materialize
the branch through the repository's normal checkout/worktree workflow.
- Otherwise, report that the review could not yet be recorded in `gh-rev` and
identify the missing local branch prerequisite. Do not fabricate a branch
ledger, substitute a different SHA, or claim a revision was submitted.
## Another independent review
Read every existing revision and GitHub review first, but independently inspect
the full change. Avoid repeating an existing unresolved finding unless new
evidence materially changes it. Allocate a new revision because this is a new
review pass, even when it concludes with approval.
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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |