craftsman

Plugin craftsman from marketplace awesome-claude-code-plugins in ccplugins/awesome-claude-code-plugins. Commands read from the repo's manifest — 1 month ago.

Skills (7)

• caveats-and-status

  Use when about to report any nontrivial task as complete — requires closing with a Caveats & status section stating what was verified, what was assumed, and what's unresolved.

• commit-craft

  Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and safe to ship.

• environment-memory

  Use before retrying any command, tool, or approach that failed once, and immediately after discovering any OS/shell/tool-specific quirk — checks and updates a stable cross-project quirks file so failed approaches are never silently repeated.

• graphify-recurring-bugs

  Use during root-cause investigation of any bug in a project that has graphify-out/graph.json — surfaces related code before grepping, flags likely duplicates of existing KNOWN_ISSUES.md entries before filing a new one, and when a match lands on a resolved entry surfaces its recorded fix so a known-g

• ideation-first

  Use before planning a new feature or greenfield refactor whose requirements aren't yet pinned down — clarifies intent through a few questions and ends with a short scope brief the planner can build on.

• logging-tradeoffs

  Use when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands.

• smallest-change-first

  Use before writing any new code, function, file, or dependency — walks a decision ladder that prefers reuse over new code, and requires asking before adding anything beyond the literal request.

Slash commands (2)

• /craftsman:init

  Detect this project's tech stack (or ask, if none is detected) and propose a CLAUDE.md/KNOWN_ISSUES.md scaffold — shows the exact content and asks for confirmation before writing anything.

• /craftsman:quick

  Route a small, explicitly-scoped change straight to the coder agent, skipping the full plan/test/review pipeline.

Subagents (10)

• coder

  Implements features and fixes bugs with the smallest possible diff — no unrelated cleanup or refactoring. Reads relevant files, makes the change, runs the build, reports the result. Invoke for: 'implement', 'add this', 'fix this bug', 'write the code for', 'build this feature'.

• debugger

  Root-cause-first debugging diagnostician. Reproduces the failure, traces it to its origin, and hands off a precise root cause + fix location + reproduction recipe — never patches symptoms, never edits code (that's coder's job). Runs the superpowers 4-phase method. Invoke for: 'debug', 'why is this f

• docs-writer

  Writes and updates README files, architecture notes, API references, and changelogs — grounded only in what the code does now, not speculation. Invoke for: 'update the README', 'write docs for', 'document this API', 'update the changelog', 'add documentation for', 'write architecture notes'.

• orchestrator

  Master coordinator that classifies a task, selects the minimal effective agent pipeline, runs agents in the correct sequence (parallel where safe), enforces plan→code→test→review→security quality gates, loops at most twice on failures, and produces a structured outcome report. Also recognizes small,

• planner

  Use before any non-trivial change to decompose a feature or bug into ordered steps, identify risks, and bound scope. Returns a plan document — does not write code or touch files. Invoke for: 'plan this', 'how should I approach', 'what files need to change for', 'break this down', 'what's the best wa

• release-prep

  Runs a pre-release checklist covering version numbers, changelogs, signing config, pinned dependencies, CI/CD readiness, and store metadata. Returns PASS/FAIL/SKIP per item with a final 'Ready to ship' verdict. Invoke for: 'ready to release', 'pre-release check', 'before I ship', 'release checklist'

• researcher

  Looks up API docs, version compatibility, and best practices by searching the codebase first, then checking installed MCP servers, then official documentation on the web. Never writes files. Invoke for: 'how does X work', 'what is the difference between', 'is X compatible with version Y', 'best prac

• reviewer

  Reviews code for correctness bugs, logic errors, API misuse, missing error handling, and unnecessary reinvention of existing library/codebase functionality. Reports CRITICAL/HIGH/MEDIUM/LOW findings — does not edit files. Invoke for: 'review', 'check this code', 'look for bugs in', 'PR review', 'che

• security

  Full-stack security audit with active grep patterns for secrets, git history scan, OWASP checks, Android/Spring platform issues, CI/CD injection risks, and AI agent over-permissioning. Returns PASS/FAIL verdict. Invoke for: 'security audit', 'find vulnerabilities', 'check for secrets', 'is this safe

• tester

  Finds coverage gaps and writes missing tests — unit, integration, and regression — then runs the suite to verify. Never modifies production code. Invoke for: 'write tests for', 'add tests', 'missing coverage in', 'regression test for', 'test this class', 'coverage gaps'.

Hooks (3)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" pretooluse-graphify-bash

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" pretooluse-graphify-read

Similar plugins