Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Review your own changes before creating a pull request. An agent skill from hegeldev/hegel-go.
Install Self Review
$ npx skills add hegeldev/hegel-go --skill self-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hegeldev/hegel-go self-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/self-review .claude/skills/self-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "self-review" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-review into .claude/skills/self-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hegeldev/hegel-go --skill self-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hegeldev/hegel-go self-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/self-review .agents/skills/self-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "self-review" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-review into .agents/skills/self-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hegeldev/hegel-go --skill self-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hegeldev/hegel-go self-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/self-review .cursor/skills/self-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "self-review" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-review into .cursor/skills/self-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hegeldev/hegel-go.git --path .claude/skills/self-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hegeldev/hegel-go --skill self-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hegeldev/hegel-go self-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/self-review .gemini/skills/self-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "self-review" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-review into .gemini/skills/self-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hegeldev/hegel-go self-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hegeldev/hegel-go --skill self-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/self-review .github/skills/self-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "self-review" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-review into .github/skills/self-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hegeldev/hegel-go --skill self-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hegeldev/hegel-go self-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/self-review .opencode/skills/self-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "self-review" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/self-review into .opencode/skills/self-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
self-review- GitHub stars
- 103
- Token cost
- ~588 tokens
- SKILL.md length
- 310 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review your own changes before creating a pull request. An agent skill from hegeldev/hegel-go.
- : about to create a PR
- SKILL.md covers Mechanical checks, Review the diff, Coverage check and Final gut check
- Calls just and git
- Finished a chunk of work
What it does
Self Review is an agent skill from hegeldev/hegel-go. Review your own changes before creating a pull request. Use this before running create-pr, or whenever you want to check that your changes are clean, correct, and well-tested. Trigger when: about to create a PR, finished a chunk of work, or asked to review changes.
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: Property-based testing for Go. The licence is MIT.
When your agent uses it
- : about to create a PR
- Finished a chunk of work
- Asked to review changes
Example prompts
- “/self-review”
What it can do on your machine
Read from SKILL.md and the folder at commit 77ceb5d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
justgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Self Review loads about 588 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 310 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hegeldev/hegel-go at commit 77ceb5d, republished under its MIT licence (© hegeldev). 310 words, ~588 tokens.
Download SKILL.mdSave it as
.claude/skills/self-review/SKILL.md (or your agent's skills folder).- name
- self-review
- description
- Review your own changes before creating a pull request. Use this before running create-pr, or whenever you want to check that your changes are clean, correct, and well-tested. Trigger when: about to create a PR, finished a chunk of work, or asked to review changes.
Self-Review
Run through these checks before creating a PR or declaring work complete. The goal is to catch the things a human reviewer would flag, before they have to.
Mechanical checks
Run all of these — they're fast and catch the most common issues:
just check # formatting, lint, docs, testsFix any failures before proceeding. Don't skip checks because they passed locally last time — the code may have changed.
Review the diff
Run git diff origin/main...HEAD and read through it. Look for:
- Dead code: unused imports, variables, functions that were left behind during refactoring.
- Redundant test logic: tests that just mirror the implementation (e.g., a test with the same switch arms as the code it's testing). Good tests validate against external reality or test behavior, not structure. If a test would still pass after introducing a bug in the code, it's not testing anything useful.
- Network calls in tests: can any test that hits the network use local fixtures instead? Keep at most one integration test that verifies the real network path works.
- Hardcoded paths:
/tmp/fooin tests should bet.TempDir()for isolation and cleanup. - Missing error context: error messages should help the user fix the problem (e.g., include "Install X manually:
<url>"). - New
// coverage-ignoreannotations: each one needs explicit human permission. Your first instinct should be to write a test or refactor for testability instead.
Coverage check
Run just test and review the output. If new code is uncovered, address it before the PR — don't rely on CI to catch it. See the coverage skill for how to approach coverage gaps.
Final gut check
Ask yourself: if someone else wrote this diff, what would I flag in code review? Common things to catch:
- Functions that panic where they should return errors (or vice versa)
- Thin wrapper functions that exist only for testability but aren't actually tested
- Comments that describe what the code does rather than why
© hegeldev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/self-review of hegeldev/hegel-go.
Open the folder on GitHubat commit 77ceb5d
Compare with similar skills
Self Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Self Review this skillhegeldev/hegel-go | 103 | — | ~588 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from hegeldev/hegel-go
Changelog
hegeldev/hegel-go
Changelog style guide for writing RELEASE.md files. An agent skill from hegeldev/hegel-go.
Coverage
hegeldev/hegel-go
How to approach code coverage in this project. An agent skill from hegeldev/hegel-go.
Go Concurrency
hegeldev/hegel-go
Go concurrency patterns and pitfalls for this codebase. An agent skill from hegeldev/hegel-go.
Align Libhegel
hegeldev/hegel-go
How to align the Go FFI wrapper to a new libhegel (hegel-c) release.
Related
Categories
Questions about Self Review
What does Self Review do?
Review your own changes before creating a pull request. An agent skill from hegeldev/hegel-go. Self Review is an agent skill from hegeldev/hegel-go. Review your own changes before creating a pull request.
When should I use Self Review?
Self Review fits situations like: : about to create a PR; finished a chunk of work; asked to review changes.
How do I install Self Review in Claude Code?
Run `npx skills add hegeldev/hegel-go --skill self-review -a claude-code`. Or copy the skill folder (.claude/skills/self-review in hegeldev/hegel-go) into .claude/skills/self-review in your project. Claude Code loads it when a task matches its description.
How do I install Self Review in Codex?
Run `npx skills add hegeldev/hegel-go --skill self-review -a codex`. Or copy the skill folder (.claude/skills/self-review in hegeldev/hegel-go) into .agents/skills/self-review in your project. Codex loads it when a task matches its description.
Can I use Self Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hegeldev/hegel-go --skill self-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/self-review, .gemini/skills/self-review, .github/skills/self-review and .opencode/skills/self-review in your project.
What does Self Review need to run?
Going by SKILL.md and its folder, Self Review needs the command-line tools its instructions call (just and git).
Does Self Review access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Self Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Self Review use?
Self Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Self Review use?
About 588 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Self Review?
Skills that share tags, products or a category with Self Review: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Self Review?
hegeldev (a GitHub organization) maintains it in hegeldev/hegel-go, which has 103 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: hegeldev/hegel-go on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.