review-issue
Skill17 starsChanged 3 months agoApache-2.0View on GitHub
Run an on-demand adversarial review of a refined cockpit issue plan. Dispatches the plan-reviewer agent against the plan in the issue description and posts the findings as a comment. Use when a human wants a fresh review of an existing plan outside the autonomous refinement flow, e.g. "review CK-12". Not part of the autonomous pipeline; the refine-issue skill already self-reviews inline.
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
- FreddyPoly/claude-skillstheir own version, first seen Sep 3, 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★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- mampfes/hacs_waste_collection_schedule★ 2.3ksame name
- normalled/apijack★ 7same name
- Minitour/agentic-ontology-development-kit★ 2same name
- ravihammond/skills★ 1same name
- FreddyPoly/claude-skills★ 0same 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 repository7 other files it gives its agents.
- accept-issueSkill
- browser-testSkill
- implement-issueSkill
- integration-testSkill
- publish-releaseSkill
- refine-issueSkill
- regen-cli-commandsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Wait for the user to confirm before changing status.
- Distinctive: line 47
Always post the findings comment.
- Distinctive: line 49
Do not change issue status without the user's say-so.
“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.
Files
Review a cockpit issue plan (on-demand)
A manual tool for getting a fresh adversarial pass on a plan that already sits in an issue's description. The autonomous pipeline does not use this: the refine-issue skill self-reviews inline during refinement and posts those findings itself. Reach for this skill when a human wants an extra review of an existing plan, for example after editing it by hand or before approving it at the Plan Review gate.
Input
The issue key (e.g. CK-12) from the invocation. If none was given, ask which issue.
Steps
1. Read the issue
mcp__cockpit-config__get_issuefor the key. One call returns the title, full description (the plan), status, and every comment — read prior review comments and any human feedback.- Extract the original brief from the plan's
## Requestblock at the top of the description. The reviewer needs it to check scope drift.
2. Determine the repo
The reviewer verifies file paths and code snippets against the actual codebase. list_projects, match the issue's projectId, and use that project's repoPath if set. Otherwise use the current working directory (today's behaviour). If neither is a code repo, the reviewer will note that code accuracy was not verified.
3. Dispatch the reviewer
Dispatch the plan-reviewer agent (subagent_type: "plan-reviewer") with three labelled blocks:
**Plan draft:**
<full issue description>
**Original brief:** <verbatim Request block from the description>
**Repo:** <resolved repo path from step 2>The agent returns Critical/High/Medium/Low findings and a PASS/FAIL verdict. It does not touch the issue.
4. Post the findings as a comment
Post the agent's full review (the four buckets and verdict) as a comment on the issue via mcp__cockpit-config__add_issue_comment. Post it regardless of verdict.
5. Report and offer to transition
Report the verdict to the user. Do not change the issue status automatically. If the user wants to act on it, offer the obvious transition:
- FAIL (Critical/High): offer to set
Refine Readyto send it back for another refinement pass. - PASS: offer to set
Implementation Readyif they are approving at the Plan Review gate.
Wait for the user to confirm before changing status.
Rules
- One review pass per invocation. No looping.
- Always post the findings comment.
- The agent reviews; this skill posts the comment. Do not duplicate the agent's reasoning here.
- Do not change issue status without the user's say-so. This is a manual tool, not an autonomous stage.
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.

