agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-tools-py/.claude/skills/issue_update/SKILL.md

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

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
  1. Very specific:

    If no issue context is found from prior analysis, respond: "No issue context found.

    line 20
  2. Very specific:

    Call mcp__mcp-workspace__github_issue_view with the issue number.

    line 23
  3. Distinctive:

    Write the issue body to a temp file (avoids bash escaping issues with markdown):

    line 29
  4. Very specific:

    Update the issue using --body-file:

    line 34

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

Update GitHub Issue

Based on our prior /issue_analyse discussion, update the GitHub issue with refined content.

Instructions:

  1. If no issue context is found from prior analysis, respond: "No issue context found. Please run /issue_analyse <number> first."
  2. First, fetch the current issue content: Call mcp__mcp-workspace__github_issue_view with the issue number.
  3. Draft updated issue text with:
    • Clear, concise title
    • Well-structured body with implementation ideas
  4. 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)
  1. Update the issue using --body-file:
gh issue edit <issue_number> --title "NEW_TITLE" --body-file .scratch/issue_body_temp.md
  1. 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 Branch section 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 Branch section

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.
  • ## Decisions table — decided topics so /issue_analyse won't re-ask. Skip if none yet.

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.