issue_approve
Skill49 starsChanged 2 days agoMITView on GitHub
Approve issue to transition to next workflow status
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-tools-pyedited, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- MarcusJellinghaus/mcp-tools-py★ 2161% same
Wrote their own version · 0
None found.
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 repository22 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- commit_pushSkill
- discussSkill
- implementation_approveSkill
- implementation_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement-directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_createSkill
- issue_requirementsSkill
- issue_updateSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- pr_comment_triageSkill
- rebaseSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If no issue number is provided:
- Very specific: line 22
Check if the issue number is known from prior /issue_analyse or /issue_create in this conversation
- Very specific: line 23
Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
- Distinctive: line 24
If still unknown, ask the user
- Very specific: line 28
If --repo owner/repo was given, compare it with origin (mcp__mcp-workspace__git, command ls_remote, args ["--get-url", "origin"]).
- Very specific: line 33
No match (or no origin) → cross-repo.
- Distinctive: line 36
No matching entry → stop and report "not a reference project".
- Very specific: line 42
Call mcp__mcp-workspace__github_issue_view with the issue number (plus reference_name for cross-repo).
- Distinctive: line 53
No blocking questions remain
- Distinctive: line 55
If any check fails, stop and report — do not approve.
- Very specific: line 78
Do not also comment /approve — the Action would race this call.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Approve Issue
Approve the current issue to transition it to the next status in the workflow.
Resolve Issue Number
The user may provide an issue number as the argument (available as $ARGUMENTS).
If no issue number is provided:
- Check if the issue number is known from prior
/issue_analyseor/issue_createin this conversation - Read
.vscodeclaude_status.txtand extract the issue number from theIssue #NNNline - If still unknown, ask the user
Cross-Repo Issues
- If
--repo owner/repowas given, compare it withorigin(mcp__mcp-workspace__git, commandls_remote, args["--get-url", "origin"]). Normalise both: accepthttps://github.com/owner/repoandgit@github.com:owner/repoforms, drop a trailing.git, compare case-insensitively. - Match → ignore
--repoentirely; follow the normal (workspace) path. - No match (or no
origin) → cross-repo. Callmcp__mcp-workspace__get_reference_projects()and pick the entry whoseurlnormalises (as above) toowner/repo. Use itsnameasreference_nameon every GitHub tool call. Entries with a nullurlnever match. - No matching entry → stop and report "not a reference project". There is no other route.
- Never pass a repo to
set-status.
Instructions
Fetch the issue to confirm it exists: Call
mcp__mcp-workspace__github_issue_viewwith the issue number (plusreference_namefor cross-repo). Cross-repo only: success means the output starts with# #<number>:, or is# #<number>followed by a newline (untrusted author; proceed normally). Anything else → "approval failed:<result>".Note its status labels (labels prefixed
status-) — step 3 uses them for the promotable check and the--from-statusvalue.Validate that the issue is ready for approval:
- Issue has been analyzed/discussed
- Requirements are clear
- No blocking questions remain
If any check fails, stop and report — do not approve.
Promote.
current next status-01:createdstatus-02:awaiting-planningstatus-04:plan-reviewstatus-05:plan-readystatus-07:code-reviewstatus-08:ready-pr- More than one status label → don't promote; report "nothing to approve (multiple status labels: X, Y)".
- Current status not in the table (including no status label) → don't promote; report "nothing to approve".
- Cross-repo → call
mcp__mcp-workspace__github_issue_comment(number=…, reference_name=…, body="/approve")and report "approval requested, not confirmed". No polling. - Otherwise run from the project directory (no
--project-dir, no output redirection — the result is printed on stderr):mcp-coder gh-tool set-status <next> --from-status <current> --issue <issue_number> --force--forceonly skips the clean-tree check, irrelevant for a label change. Do not also comment/approve— the Action would race this call.
Report the issue number and the outcome:
set-statusresultReport exit 0, Updated issue #N to <next><current> → <next>exit 0, Skipped set-status to '…': current label is 'X', expected 'Y'"not approved (current status X)" non-zero exit "approval failed: <error output>" — stop; no retry, no/approvefallbackCross-repo comment result Report starts with Added comment to issue #"approval requested, not confirmed" anything else "approval failed: <result>" — no retryNot-called outcomes are reported as stated in step 3.
Note: This skill has disable-model-invocation — it can only be run by the user typing /issue_approve. If you need this skill as a follow-up, tell the user: "Please run /issue_approve to proceed."
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.

