agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-workspace/.claude/skills/issue_analyse/SKILL.md

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

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
  1. Distinctive:

    If no issue number is provided:

    line 18
  2. Very specific:

    Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line

    line 19
  3. Distinctive:

    If the file doesn't exist or has no issue number, ask the user

    line 20
  4. Distinctive:

    Read linked issues first: If the issue points to an epic, design doc, dependencies, or sibling issues, read those before analysing — it may …

    line 24
  5. Distinctive:

    Do not provide code yet!

    line 32
  6. Very specific:

    If the issue contains a ## Decisions section, read it carefully:

    line 37
  7. Distinctive:

    Do NOT re-ask topics that are already decided.

    line 38
  8. Distinctive:

    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.

    line 39
  9. Very specific:

    If the issue contains a ### Base Branch section:

    line 45
  10. Very specific:

    Verify the branch exists using: call mcp__mcp-workspace__git with command "ls_remote" and args ["--heads", "origin", "<branch-name>"]

    line 47
  11. Distinctive:

    If the branch does NOT exist, show a clear warning: "⚠️ Warning: Base branch 'X' does not exist on remote.

    line 48

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
  2. 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__git with 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.