review-issue
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Run an OPTIONAL, independent second-opinion review of one already-implemented issue's diff, using a dedicated Opus subagent so the review judgment is always high-quality regardless of what model is driving the current session. This is NOT a required gate — issues.md/qc do not wait on it, and skipping it is completely fine. Use it when the user wants extra scrutiny on a specific done issue before moving on, or invokes /review-issue explicitly. Only picks up issues already marked `done ⚠️ pending-review` by implement-issue (its own code-review/security-review already ran); if none exist, say so and stop. Distinct from the code-review and security-review skills: those run inside the same session that just implemented the issue and check general code quality / security respectively, while review-issue is a deliberately fresh, later, independent pass focused specifically on whether the diff actually conforms to SPEC.md and the issue's acceptance criteria — catching cases where the implementing agent's own self-assessment was wrong. On finding a real conformance failure or bug, reopens the issue with feedback exactly like qc does; nitpicks are reported but don't block. Requires an issues/ folder with at least one done ⚠️ pending-review issue — if none, there's nothing for this skill to do yet.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- normalled/apijacktheir own version, first seen Nov 8, 2026
- mampfes/hacs_waste_collection_scheduletheir own version, first seen Oct 8, 2026
- PrefectHQ/fastmcptheir own version, first seen Oct 8, 2026
- jlowin/fastmcptheir own version, first seen Oct 8, 2026
- alexjbarnes/cockpittheir own version, first seen Aug 13, 2026
- Minitour/agentic-ontology-development-kittheir own version, first seen Jul 24, 2026
Used with
Projects with it also use review-pr and release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- PrefectHQ/fastmcp★ 28ksame name
- jlowin/fastmcp★ 28ksame name
- mampfes/hacs_waste_collection_schedule★ 2.3ksame name
- alexjbarnes/cockpit★ 16same name
- normalled/apijack★ 7same name
- Minitour/agentic-ontology-development-kit★ 2same name
- ravihammond/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- doc-to-issuesSkill
- documentationSkill
- implement-backlogSkill
- implement-issueSkill
- interviewSkill
- polishSkill
- qcSkill
- reportSkill
- staging-qa-docSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.