Plugin development ยท 22 skills, 7 agents, 2 commands
engineering
Engineering workflow skills, review agents, and a /feature pipeline: orientation, planning, test-driven development, systematic debugging, refactoring, error handling, observability, containers, CI pipelines, dependency upgrades, migration planning, incident postmortems, code review, completion verification, and performance work.
workflowtdddebuggingcode-reviewplanning
Install
Add the marketplace once, then install the bundle. Claude Code namespaces its commands (/engineering:name), wires any hooks, and updates it with /plugin marketplace update dotclaude.
/plugin marketplace add KhaledSaeed18/dotclaude/plugin install engineering@dotclaudeWhat you get
Skills (22)
- adversarial-reviewerReview code through three hostile personas - the Saboteur, the New Hire, and the Security Auditor - each required to find at least one issue. Use when a...
- api-design-reviewReview an API contract (REST or GraphQL) before or while it is implemented, checking resource naming, HTTP semantics, status codes, error shape...
- code-review-responseProcess code-review feedback with technical rigour. Understand each point, check it against the actual codebase, and respond with reasoning or...
- db-migration-safetyReview or write a database schema migration with production safety as the bar, checking locks, table rewrites, backfills, expand-contract deploy order...
- dependency-upgradeUpgrade dependencies without breaking the project: audit what is outdated and why it matters (security, EOL, features), read the changelogs and migration...
- dockerfile-best-practicesWrite or review a Dockerfile and compose setup for a production service: multi-stage builds that ship only the runtime, pinned base images, layer order...
- error-handling-patternsDesign and review error handling in a codebase: which errors are expected results versus bugs, typed error hierarchies or result types, where to catch...
- executing-plansExecute a written implementation plan task by task, reviewing it critically first, following each step exactly, running every verification, and stopping...
- explain-codebaseOnboard to an unfamiliar codebase by mapping its architecture, entry points, and data flow. Use when starting work in a new or unknown repository and you...
- fix-ciDiagnose and fix a failing CI run by pulling the actual failure logs (gh run view --log-failed), reproducing the failure locally, fixing the root cause...
- github-actions-pipelineDesign, write, or fix GitHub Actions workflows for a project: a CI pipeline with the right triggers, concurrency, caching, matrix, and least-privilege...
- grill-with-docsStress-test a plan against the project's existing domain model by challenging terminology, surfacing contradictions with code, and updating CONTEXT.md and...
- incident-postmortemWrite a blameless incident postmortem from the timeline, logs, chat transcripts, and the fix: impact with numbers, a minute-by-minute timeline, root cause...
- logging-and-observabilityInstrument a service so production problems are diagnosable: structured JSON logs with consistent fields and levels, correlation ids across requests and...
- parallel-agentsFan independent work out to multiple subagents that run concurrently, each with a focused scope and self-contained instructions, then review and integrate...
- performance-optimizationFix a performance problem by profiling first, making one targeted change, and verifying both the speedup and that correctness held. Use when a feature is...
- refactoring-recipesRefactor safely by name: a catalogue of the refactorings that come up in practice (extract function or module, inline, rename, replace conditional with...
- solid-principlesApply the SOLID principles as design diagnostics, detecting god classes, fragile hierarchies, fat interfaces, and hard-wired dependencies, and prescribing...
- systematic-debuggingDebug a bug, test failure, crash, or unexpected behaviour by finding the root cause before changing anything, instead of guessing at fixes. Works in any...
- test-driven-developmentImplement a feature or bugfix test-first using the red-green-refactor cycle. Write a failing test, watch it fail, write the minimal code to pass, then...
- verify-completionGate every "it works / it's fixed / tests pass / done" claim behind fresh evidence. Run the actual verifying command, read its output, and only then state...
- writing-plansTurn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context....
Agents (7)
- architect-reviewerUse this agent when you need a design-level architecture review of a module, a proposed change, or a whole codebase. Evaluates boundaries, coupling and...
- code-reviewerExpert reviewer for a code change (a diff, a staged set, a branch, or named files). Reviews for correctness, security, and maintainability across...
- debuggerUse this agent when you need a bug, test failure, crash, or unexpected behaviour diagnosed through systematic root-cause analysis. Gathers evidence, tests...
- docs-writerUse this agent when you need documentation written or updated from the code itself, such as READMEs, API references, guides, architecture overviews, or...
- error-detectiveUse this agent when you need errors, stack traces, and logs correlated across services or files to find the root cause of an incident or recurring...
- migration-plannerUse this agent to plan a large, risky change as a sequence of small reversible steps: a framework or runtime major upgrade, a database or storage...
- performance-engineerUse this agent when you need a performance problem investigated, measured, and resolved end-to-end. Profiles the running system, finds the real bottleneck...
Commands (2)
- explain-codeWalk through a file, function, class, or module and explain what it does, how it works, and why it is structured that way. Pass a file path or a symbol...
- featureTake a feature from a one-line description to a reviewed, tested change through a fixed pipeline: orient with the code-explorer agent, clarify...