api-documentation
When consumers need to know how to call your API — endpoint docs, OpenAPI specs, request/response examples.
24 skills tagged ship · lifecycle axis.
When consumers need to know how to call your API — endpoint docs, OpenAPI specs, request/response examples.
When users need to know what changed and why — conventional commits parsing, semantic versioning, release notes.
When you need CI that catches failures before they hit main — generates GitHub Actions/GitLab CI with artifact gating.
When a PR needs more than a thumbs-up — review checklists, defect categories, severity classification.
When your supply chain is only as strong as its weakest dep — checks for CVEs and license compliance.
When your Docker image is bloated and slow to build — generates optimized multi-stage Dockerfiles.
When the team needs git discipline without git fights — branching strategies, commit conventions, conflict resolution.
When unit tests pass but the system doesn't work — tests across component boundaries with Docker containers.
When you need reproducible K8s deployments — generates Helm charts and Kubernetes manifests.
When you suspect tests pass but don't actually catch bugs — verifies test quality by injecting faults.
When your API docs are stale or missing — generates Swagger/OpenAPI YAML from code.
When the app is slow but you don't know where — bottleneck identification, complexity analysis, caching review.
When PRs linger or get rubber-stamped — templates, review assignments, merge criteria that work.
Master workflow for thorough PR review. Orchestrates code-review + security-review + performance-review in parallel, aggregates verdict, applies pr-management, audits. No implementation logic.
When a new contributor clones the repo and has no idea where to start — creates READMEs with usage and install guides.
When release day shouldn't mean manually writing changelog — parses git logs for changelogs and version bumps.
Master workflow for cutting a release. Orchestrates test-strategy -> changelog-generation -> ci-pipeline -> auditor as a single named sequence. No implementation logic.
When code needs a security audit before shipping — scans for OWASP Top 10 vulnerabilities and anti-patterns.
When security can't be an afterthought — OWASP Top 10 scan, vulnerability detection, secret scanning.
When infrastructure should be versioned like code — generates Terraform/OpenTofu IaC modules.
When you need a testing philosophy, not just tests — defines the pyramid, coverage targets, and conventions.
When you're unsure what to test next — coverage analysis, test type selection, boundary condition identification.
When you need metrics without false-failing the build — separates collection (Pass 1) from gating (Pass 2).
When a function needs proof it works — generates unit tests for Jest, JUnit, Go Test, PyTest.