What is implement-github-issue?

A command that guides implementation of a GitHub issue, a tracked task or bug in a code repository.

Use it to analyze an issue, identify affected files, create a branch, implement the change, and add unit and property-based tests.

It turns an issue into a planned development process, including codebase research, a feature branch, implementation, and tests.

How sapientpants/deepsource-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sapientpants/deepsource-mcp-server. 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/sapientpants/deepsource-mcp-server/main/.claude/commands/implement-github-issue.md

Clone the repo

git clone --depth 1 https://github.com/sapientpants/deepsource-mcp-server

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/commands/sapientpants/deepsource-mcp-server/implement-github-issue/github.svg)](https://agentmods.dev/commands/sapientpants/deepsource-mcp-server/implement-github-issue)

Your own site

<a href="https://agentmods.dev/commands/sapientpants/deepsource-mcp-server/implement-github-issue"><img src="https://agentmods.dev/badge/commands/sapientpants/deepsource-mcp-server/implement-github-issue/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/commands/sapientpants/deepsource-mcp-server/implement-github-issue"><img src="https://agentmods.dev/badge/commands/sapientpants/deepsource-mcp-server/implement-github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 863 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 original No closer match found 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.00000	$0.00863
Opus 5.5	$0.00000	$0.00345
Sonnet 5.5	$0.00000	$0.00173
Haiku 4.5	$0.00000	$0.00086

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

Security

Grade A, and why

implement-github-issue 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 2mo 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.

.claude/commands/implement-github-issue.md · 166 lines

How it starts

The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement GitHub Issue

You are about to implement GitHub issue: $ARGUMENTS

Implementation Workflow

1. Analyze the Issue

gh issue view $ARGUMENTS

Review the full issue description
If it contains Gherkin specs, parse acceptance criteria carefully
Identify non-goals and constraints
Note any technical requirements

2. Research Codebase

Search for relevant existing code
Identify files needing modification
Look for similar patterns to maintain consistency
Review existing tests for patterns

3. Plan Implementation

Create a plan with:

Core functionality breakdown
Test strategy (unit + property-based)
Files to create/modify
Edge cases and risks

4. Create Feature Branch

# Follow branch naming from CLAUDE.md
git checkout -b <type>/<issue-number>-<description>
# Example: feat/42-user-authentication

5. Implement Solution

Follow patterns in CLAUDE.md (validation, testing, imports)
Write clean, focused functions
Add TypeScript types and Zod validation
Document public APIs with JSDoc

6. Write Tests

Required test coverage:

Unit tests in tests/*.spec.ts
Property-based tests in tests/*.property.spec.ts for business logic
Test both success and failure cases
Verify edge cases

7. Verify Quality

pnpm verify  # Runs all checks

8. Create Changeset

Changeset Guidance for Features:

# For bug fixes
pnpm changeset
# Select: patch
# Message: "Fix: [brief description of what was fixed]"

# For new features
pnpm changeset
# Select: minor
# Message: "Add [feature name]: [brief description]"

# For breaking changes
pnpm changeset
# Select: major
# Message: "BREAKING: [what changed and migration required]"

# For non-code changes (docs, tests, refactoring)
pnpm changeset --empty
# Message: "Internal: [what was changed]"

Decision Guide:

patch: Bug fixes, security patches, performance improvements
minor: New features, new APIs, significant enhancements
major: Breaking changes, API removals, incompatible updates
--empty: Documentation, tests, CI/CD, internal refactoring

Read the full file on GitHub · 166 lines

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.

2mo ago First seen · 166 lines · 0 tokens per session scan A 2bfe9a3c4c86

Subscribe to this mod's changes

implement-github-issue is a command published in the GitHub repository sapientpants/deepsource-mcp-server (7 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 863 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Project management deepsource mcp mcp-server model-context-protocol model-context-protocol-servers

implement-github-issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implement-github-issuesapientpants/deepsource-mcp-server	Command	7	1y ago	MIT	A	0	Claude Code
list_checkpointsZoeLinUTS/MagicTeX-mcp	Command	4	3d ago	AGPL-3.0	A	14	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code

deepsource-mcp-server: Command for Claude Code