What is issue_approve?

An issue-workflow skill for approving a GitHub issue so it can move to its next status.

Use it to check the issue, confirm that requirements are clear and no blocking questions remain, and add the approval comment.

It prevents issues from advancing before they have been reviewed, discussed, and made clear enough to act on.

How MarcusJellinghaus/mcp-tools-sql configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MarcusJellinghaus/mcp-tools-sql. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-tools-sql/main/.claude/skills/issue_approve/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sql

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_approve/github.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/issue_approve)

Your own site

<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/issue_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_approve/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/issue_approve"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/issue_approve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 519 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 94% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00008	$0.00519
Opus 5.5	$0.00003	$0.00208
Sonnet 5.5	$0.00002	$0.00104
Haiku 4.5	$0.00001	$0.00052

Measured 1mo ago against content hash 70a14843a5c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue_approve scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

94% identical to issue_approve — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/issue_approve/SKILL.md · 53 lines

What it actually says

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:

Check if the issue number is known from prior /issue_analyse or /issue_create in this conversation
Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
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

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).
Validate that the issue is ready for approval:
- Issue has been analyzed/discussed
- Requirements are clear
- No blocking questions remain
If any check fails, stop and report — do not approve.
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).

Report the issue number and the approval result.

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."

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 53 lines · 8 tokens per session scan A 70a14843a5c3

Subscribe to this mod's changes

issue_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 519 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to issue_approve, differing in 4 lines, and is treated as a copy.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

mcp-tools-sql: Skill for Claude Code