issue_update
Skill21 starsChanged 3 months agoMITView on GitHub
Update GitHub issue with refined content from analysis discussion
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★ 4943% 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_approveSkill
- issue_createSkill
- issue_requirementsSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- rebaseSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If no issue context is found from prior analysis, respond: "No issue context found.
- Very specific: line 23
Call mcp__mcp-workspace__github_issue_view with the issue number.
- Distinctive: line 29
Write the issue body to a temp file (avoids bash escaping issues with markdown):
- Very specific: line 34
Update the issue using --body-file:
≈ “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
Update GitHub Issue
Based on our prior /issue_analyse discussion, update the GitHub issue with refined content.
Instructions:
- If no issue context is found from prior analysis, respond: "No issue context found. Please run
/issue_analyse <number>first." - First, fetch the current issue content:
Call
mcp__mcp-workspace__github_issue_viewwith the issue number. - Draft updated issue text with:
- Clear, concise title
- Well-structured body with implementation ideas
- Write the issue body to a temp file (avoids bash escaping issues with markdown):
mcp__mcp-workspace__save_file(file_path=".scratch/issue_body_temp.md", content=body_content)- Update the issue using
--body-file:
gh issue edit <issue_number> --title "NEW_TITLE" --body-file .scratch/issue_body_temp.md- Clean up the temp file:
mcp__mcp-workspace__delete_this_file(file_path=".scratch/issue_body_temp.md")Editing Base Branch:
- To add a base branch: Insert
### Base Branchsection with the branch name - To change a base branch: Update the content under the existing section
- To remove a base branch: Delete the entire
### Base Branchsection
The base branch must be a single line. Multiple lines will cause an error during branch creation.
The updated issue should include:
- Summary of the requirement
- Discussed implementation approach (concise)
## Constraints & Rationale— non-obvious gotchas and the "why" behind decisions. Skip if none identified.## Decisionstable — decided topics so/issue_analysewon't re-ask. Skip if none yet.
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.

