ImperialAutomation/claude-code-toolkit

Claude Code skills for GitHub issue management, PR workflows, and development utilities

11Stars on the repository
30Mods indexed here, across every type
4d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

kickoff

12

ImperialAutomation/claude-code-toolkit

Skill Claude CodeCodex

Project kickoff checklist based on lessons learned from previous projects. Generates a tailored checklist and optionally creates GitHub issues.

11 4d ago A 25 tokens

promote

14

ImperialAutomation/claude-code-toolkit

Skill Claude CodeCodex

Promote a project-local script or procedure to the shared toolkit. Generalises the implementation and creates a thin project-local wrapper.

11 4d ago A 28 tokens

release-pr

16

ImperialAutomation/claude-code-toolkit

Skill Claude CodeCodex

Create the develop → master release PR — inspect what changed since the last tag, decide the semver bump, apply the release:major/minor/patch label so the tag is generated correctly, and write the release body. Use for "release to master", "promote develop", "make a release PR", "cut a release", "new version tag".

11 4d ago A 76 tokens

retro

17

ImperialAutomation/claude-code-toolkit

Skill Claude CodeCodex

End-of-session retrospective. Captures knowledge from any working session (debug, implementation, config, deployment) as reusable scripts, CLAUDE.md procedures, or skill proposals. Run before ending a session to prevent knowledge loss.

11 4d ago A 47 tokens

stripe-testing

21

ImperialAutomation/claude-code-toolkit

Skill Claude CodeCodex

Stripe test values and testing procedures — test card numbers, PaymentMethod/token IDs, declines and decline codes, 3D Secure/SCA authentication cards, disputes and evidence values, async refunds, Radar/fraud simulation, SEPA Direct Debit and ACH test accounts, webhook triggering, and test-mode rate limits. TRIGGER …

11 4d ago A 202 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: