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

issue_approve

Skill21 starsChanged 3 months agoMITView on GitHub

Approve issue to transition to next workflow status

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

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

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

    Check if the issue number is known from prior /issue_analyse or /issue_create in this conversation

    line 20
  3. Very specific:

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

    line 21
  4. Distinctive:

    If still unknown, ask the user

    line 22
  5. Very specific:

    If a --repo owner/repo flag was given, append it to every gh command below, and fetch the issue with gh issue view <issue_number> --repo …

    line 26
  6. Very specific:

    Call mcp__mcp-workspace__github_issue_view with the issue number (or gh issue view for cross-repo).

    line 33
  7. Distinctive:

    No blocking questions remain

    line 38

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

Approve Issue

Approve the current issue to transition it to the next status in the workflow.

Resolve Issue Number

The user may provide an issue number as the argument (available as $ARGUMENTS). If no issue number is provided:

  1. Check if the issue number is known from prior /issue_analyse or /issue_create in this conversation
  2. Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
  3. If still unknown, ask the user

Cross-Repo Issues

If a --repo owner/repo flag was given, append it to every gh command below, and fetch the issue with gh issue view <issue_number> --repo owner/repo via Bash — mcp__mcp-workspace__github_issue_view only reaches the current repository.

Instructions

  1. Fetch the issue to confirm it exists: Call mcp__mcp-workspace__github_issue_view with the issue number (or gh issue view for cross-repo).
  2. Validate that the issue is ready for approval:
    • Issue has been analyzed/discussed
    • Requirements are clear
    • No blocking questions remain
  3. Comment /approve on the issue (use MSYS_NO_PATHCONV to prevent Windows Git Bash path conversion):
MSYS_NO_PATHCONV=1 gh issue comment <issue_number> --body "/approve"

This triggers the GitHub Action to promote the issue status (e.g., status-01:created → status-02:awaiting-planning).

Note: This skill has disable-model-invocation — it can only be run by the user typing /issue_approve. If you need this skill as a follow-up, tell the user: "Please run /issue_approve to proceed."

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.