issue_analyse
Skill49 starsChanged 2 days agoMITView on GitHub
Analyse GitHub issue requirements, feasibility, and implementation approaches
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★ 2191% 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_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
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 18
If no issue number is provided:
- Very specific: line 19
Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
- Distinctive: line 20
If the file doesn't exist or has no issue number, ask the user
- Distinctive: line 24
Read linked issues first: If the issue points to an epic, design doc, dependencies, or sibling issues, read those before analysing — it may …
- Distinctive: line 32
Do not provide code yet!
- Very specific: line 37
If the issue contains a ## Decisions section, read it carefully:
- Distinctive: line 38
Do NOT re-ask topics that are already decided.
- Distinctive: line 39
If any existing decision seems risky or questionable given what you see in the code, briefly note the concern — but don't block on it.
- Very specific: line 45
If the issue contains a ### Base Branch section:
- Very specific: line 47
Verify the branch exists using: call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", "origin", "<branch-name>"]
- Distinctive: line 48
If the branch does NOT exist, show a clear warning: "⚠️ Warning: Base branch 'X' does not exist on remote.
≈ “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
Analyse GitHub Issue
Fetch a GitHub issue and analyze its requirements, feasibility, and potential implementation approaches.
Resolve Issue Number
The user may provide an issue number as the argument (available as $ARGUMENTS).
If no issue number is provided:
- Read
.vscodeclaude_status.txtand extract the issue number from theIssue #NNNline - If the file doesn't exist or has no issue number, ask the user
Fetch the issue using mcp__mcp-workspace__github_issue_view.
Read linked issues first. If the issue points to an epic, design doc, dependencies, or sibling issues, read those before analysing — it may not be self-contained, and any "read first" note is mandatory.
Instructions
Analyze the issue:
Can we discuss this requirement / implementation idea and its feasibility? Please also look at the code base to understand the context (using the different tools with access to the project directory). Do not provide code yet!
At the end of our discussion, I want to have an even better issue description.
Decision-awareness:
If the issue contains a ## Decisions section, read it carefully:
- Do NOT re-ask topics that are already decided. Focus on aspects not yet covered.
- If any existing decision seems risky or questionable given what you see in the code, briefly note the concern — but don't block on it.
Constraints identification:
During the discussion, actively identify constraints and rationale — the "why" behind decisions, non-obvious gotchas, things that downstream steps (/create_plan, /implement) need to know. These will be captured in the issue via /issue_update.
Base Branch Handling:
If the issue contains a ### Base Branch section:
- Display the specified base branch prominently
- Verify the branch exists using: call
mcp__mcp-workspace__gitwith command"ls_remote"and args["--heads", "origin", "<branch-name>"] - If the branch does NOT exist, show a clear warning: "⚠️ Warning: Base branch 'X' does not exist on remote. Branch creation will fail."
- Continue with the analysis (non-blocking error)
Focus on:
- Understanding the problem/feature request
- Technical feasibility
- Potential implementation approaches
- Questions that need clarification
- Impact on existing code
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.

