issue_approve
Skill21 starsChanged 3 months 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-workspaceedited, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- MarcusJellinghaus/mcp-workspace★ 4929% 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 repository21 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
- rebaseSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
If no issue number is provided:
- Very specific: line 20
Check if the issue number is known from prior /issue_analyse or /issue_create in this conversation
- Very specific: line 21
Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
- Distinctive: line 22
If still unknown, ask the user
- Very specific: line 26
If a --repo owner/repo flag was given, append it to every gh command below, and fetch the issue with gh issue view <issue_number> --repo …
- Very specific: line 33
Call mcp__mcp-workspace__github_issue_view with the issue number (or gh issue view for cross-repo).
- Distinctive: line 38
No blocking questions remain
≈ “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 a --repo owner/repo flag was given, append it to every gh command below, and fetch the
issue with gh issue view <issue_number> --repo owner/repo via Bash —
mcp__mcp-workspace__github_issue_view only reaches the current repository.
Instructions
- Fetch the issue to confirm it exists:
Call
mcp__mcp-workspace__github_issue_viewwith the issue number (orgh issue viewfor cross-repo). - Validate that the issue is ready for approval:
- Issue has been analyzed/discussed
- Requirements are clear
- No blocking questions remain
- Comment
/approveon the issue (use MSYS_NO_PATHCONV to prevent Windows Git Bash path conversion):
MSYS_NO_PATHCONV=1 gh issue comment <issue_number> --body "/approve"This triggers the GitHub Action to promote the issue status (e.g., status-01:created → status-02:awaiting-planning).
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.

