What is cleanup-issues?

A command for reviewing open GitHub issues and aligning their titles and labels with the project's commit message rules. Commitlint conventions are shared rules for prefixes such as feat or fix.

It helps list open issues, inspect the commitlint configuration, map issue content to prefixes, and add suitable labels.

It removes the manual work of finding inconsistent issue titles, choosing labels, and creating missing labels.

cleanup-issues — Command by sapientpants

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/sapientpants/deepsource-mcp-server/cleanup-issues

Clone the repo

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

Made for: Claude Code.

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 977 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00000	$0.00977
Opus 5	$0.00000	$0.00489
Sonnet 5	$0.00000	$0.00195
Haiku 4.5	$0.00000	$0.00098

Measured 2d ago against content hash d40a1ba2cf97, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cleanup-issues 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 2d 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/cleanup-issues.md · 105 lines

How it starts

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

cleanup-issues

Clean up GitHub issues by aligning prefixes with commitlint conventions and adding appropriate labels based on content.

Steps to Execute

List all open issues to review:

gh issue list --state open --limit 100 --json number,title,labels

Check the commitlint configuration for valid prefixes:
- Read commitlint.config.js to see allowed types
- Valid prefixes: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

Create missing labels if needed:

gh label create "performance" --description "Performance improvements" --color "1d76db"
gh label create "refactoring" --description "Code refactoring" --color "d4c5f9"
gh label create "security" --description "Security improvements" --color "d73a4a"
gh label create "technical-debt" --description "Technical debt" --color "fef2c0"
gh label create "reliability" --description "Reliability improvements" --color "0e8a16"

For each issue, analyze the content and update if needed:

Prefix Mapping Rules:

Issue Content	Correct Prefix	Labels to Add
New feature, pagination, retry mechanism	`feat:`	enhancement, reliability (if resilience)
Bug fix, security fix, validation fix	`fix:`	bug, security (if security-related)
Performance optimization, caching, query optimization	`perf:`	performance
Code restructuring, normalization, consolidation	`refactor:`	refactoring, technical-debt
Dependency management, versioning, cleanup	`chore:`	dependencies, technical-debt
Documentation updates	`docs:`	documentation
Test additions or changes	`test:`	testing

Read the full file on GitHub · 105 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.

2d ago First seen · 105 lines · 0 tokens per session scan A d40a1ba2cf97

Subscribe to this mod's changes

cleanup-issues is a command published in the GitHub repository sapientpants/deepsource-mcp-server (7 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 977 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.

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

cleanup-issues

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

cleanup-issues

Steps to Execute

What this file has done since we first saw it

Other commands, from other repositories

push

qland

commit

methodology

release

compile