implementation_approve
Skill49 starsChanged 2 days agoMITView on GitHub
Approve implementation and transition issue to PR-ready state
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★ 2169% 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_finaliseSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement-directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- 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
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 17
If branch-status reports a base branch other than main, ask the user to confirm this is intentional before proceeding.
- Very specific: line 19
Only if the report's Recommendations: line contains Ready to merge, run the set-status command and confirm it succeeded: The line is …
- Very specific: line 25
Note: If Ready to merge is absent, report the blockers to the user and do not set the label.
- Very specific: line 29
After the label is set, poll for the PR to be created and pass CI: Call mcp__mcp-workspace__check_branch_status.
≈ “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 Implementation
Approve the implementation and transition the issue to PR-ready state.
Instructions:
- Run branch-status check:
Call
mcp__mcp-workspace__check_branch_status. - If
branch-statusreports a base branch other thanmain, ask the user to confirm this is intentional before proceeding. - Only if the report's
Recommendations:line containsReady to merge, run the set-status command and confirm it succeeded: The line is comma-separated (e.g.Recommendations: Ready to merge (squash-merge safe), ...);Ready to merge (squash-merge safe)counts. The match is case-sensitive: the blocking recommendationNot ready to merge (GitHub mergeable_state: ...)has a lowercaserand must not satisfy the check.
mcp-coder gh-tool set-status status-08:ready-prNote: If Ready to merge is absent, report the blockers to the user and do not set the label. If the set-status command fails, report the error to the user. Do not use --force unless explicitly asked.
Effect: Changes issue status from status-07:code-review to status-08:ready-pr.
- After the label is set, poll for the PR to be created and pass CI:
Call
mcp__mcp-workspace__check_branch_status.
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.

