documentation-api-reference

More from kentoshimizu/sw-agent-skills

• github-codeowners-management

  Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.

  9

• git-bisect-debugging

  Locate regression-introducing commits using git bisect with deterministic classification. Use when a reproducible regression exists but the introducing commit is unknown; do not use for CI workflow design or application behavior implementation.

  5

• javascript-style-guide

  Style, review, and refactoring standards for JavaScript codebases with explicit runtime contracts, safe async behavior, and maintainable module boundaries. Use when `.js`, `.jsx`, `.mjs`, or `.cjs` artifacts are created, changed, or reviewed and JS-specific quality rules must be enforced. Do not use for `.ts`, `.tsx`, `.d.ts`, or `tsconfig*.json`-owned code. For shared JS/TS config files, run together with `typescript-style-guide` when both JS and TS artifacts change in the same pull request.

  5

• algorithm-complexity-analysis

  Analyze candidate algorithms for time/space complexity, scalability limits, and resource-budget fit (CPU, memory, I/O, concurrency). Use when feasibility depends on input growth or latency/memory constraints and quantitative bounds are required before implementation; do not use for persistence schema or deployment topology decisions.

  5