adr-management
When you need to record why a decision was made — creates and manages Architecture Decision Records.
#reversible
38 skills tagged reversible · risk axis.
api-documentation
When consumers need to know how to call your API — endpoint docs, OpenAPI specs, request/response examples.
api-implementation
When the API contract is ready and needs code behind it — implements handlers/controllers with validation.
caching-strategy
When the same expensive query runs hundreds of times — implements caching patterns with proper invalidation.
changelog-generation
When users need to know what changed and why — conventional commits parsing, semantic versioning, release notes.
ci-pipeline
When you need CI that catches failures before they hit main — generates GitHub Actions/GitLab CI with artifact gating.
cleanup
When the codebase has accumulated cruft — removes noise, enforces formatting, safely renames identifiers.
code-generation
When you have a spec and need idiomatic code — generates from specs with language convention enforcement.
data-access
When your API is fast but your database calls aren't — repository pattern, query optimization, N+1 prevention.
db-tuning
When queries are the bottleneck — index analysis, query plan optimization, connection pooling.
decision-records
When future-you needs to know why past-you chose this — ADR authoring with context, decision, consequences.
dependency-updates
When dependencies drift and Dependabot floods you with PRs — automated updates with semver and lockfile discipline.
docker-containerization
When your Docker image is bloated and slow to build — generates optimized multi-stage Dockerfiles.
error-handling
When every module handles errors differently — standardizes error types, logging, and response formats.
error-handling-debug
When errors cascade instead of being contained — exception hierarchies, retry strategies, graceful degradation.
feature-shipping
Master workflow for shipping a feature end-to-end. Orchestrates prd -> task-decomposition -> tdd-workflow -> code-review -> release-pipeline -> auditor. Composes the release-pipeline master as the delivery sub-workflow.
git-workflow
When the team needs git discipline without git fights — branching strategies, commit conventions, conflict resolution.
inline-documentation
When code needs to explain itself to future readers — JSDoc/docstrings, comment quality, self-documenting patterns.
integration-testing
When unit tests pass but the system doesn't work — tests across component boundaries with Docker containers.
knowledge-sharing
When tribal knowledge walks out the door with departing teammates — wikis, runbooks, onboarding guides.
monitoring-setup
When you need to know something is broken before users tell you — SLIs/SLOs, alerting, distributed tracing.
mutation-testing
When you suspect tests pass but don't actually catch bugs — verifies test quality by injecting faults.
openapi-specs
When your API docs are stale or missing — generates Swagger/OpenAPI YAML from code.
pipeline-context
Pre-compute once, share via context object to all pipeline stages.
pr-management
When PRs linger or get rubber-stamped — templates, review assignments, merge criteria that work.
prd
When requirements exist but need structure — selects the right PRD format (lean, full, working-backwards, hypothesis) and produces a living document with versioning and lifecycle.
progressive-execution
Fast approximate results (Phase 1) then slow enriched results (Phase 2).
readme-generation
When a new contributor clones the repo and has no idea where to start — creates READMEs with usage and install guides.
refactoring
When code needs restructuring but tests must stay green — safe refactoring with test-first verification.
refactoring-suite
When you need to restructure code without breaking behavior — complex refactors with strict test verification.
refactoring-workflow
Master workflow for refactoring at four named depth levels (cosmetic, micro, meso, architectural) that compose as a ladder. Always runs chesterton-fence + style-conformance up front, closes with characterisation tests + minimal-diff + auditor. No skipped rungs.
release-notes
When release day shouldn't mean manually writing changelog — parses git logs for changelogs and version bumps.
repo-maintenance
Adaptive cleanup framework — start simple, discover value, pivot toward greater good.
resilience-patterns
Circuit breaker, retry with backoff, bulkhead isolation, fallback chains, timeouts.
schema-driven-config
Single schema powers defaults, validation, storage, and UI generation.
scorer-pipeline
Composable evaluation — independent micro-scorers with shared context and explicit weights.
tdd-workflow
When you want tests to drive the design — Red-Green-Refactor cycle with coverage targets.
unit-testing
When a function needs proof it works — generates unit tests for Jest, JUnit, Go Test, PyTest.