Menú
Dev Life Cycle quality gates: run security scans, code quality checks, performance analysis, test coverage, and PR review compliance. Routes to domain-specific sub-skills or runs all checks in sequence.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Consult external AI council (Gemini 3.5 Flash, Codex, Qwen, GLM-5.2, Kimi) for thorough reviews and consensus-driven decisions. Use ONLY when explicitly invoked with "/council" or when user says "consult the council", "invoke council", or "council review". Do NOT auto-trigger on generic phrases like "thorough review".
PR babysitter: monitors CI status, auto-rebases when behind, auto-fixes CI where possible, delegates review comment handling to dlc:pr-check, and re-requests review after fixes. Designed for /loop usage with Remote Control.
Council review reference data — expertise weights, structured response format, scoring thresholds, and false positive taxonomy. Background knowledge for council subagents.
Audit review checklist for a repo: cluster recurring review-comment themes across merged PRs in a window, diff against docs/code-review-checklist.md, and open a PR proposing new entries with PR traceability. Designed for /schedule monthly cadence. Pass --dry-run to print clusters without opening a PR. Trigger phrases: audit review checklist, update review checklist, cluster PR findings.
Multi-agent development workflow using Agent Teams. Supports five modes: plan (architect teammate + PM teammate debate → plan.md), dev (developer teammate + code-tester teammate + qa-tester teammate + reviewer teammate iterate → code), full (plan → approval gate → dev), auto (plan → dev, no gate), and bugfix (tester + developer + reviewer TDD triad → fix + PR). Use when tasks benefit from collaborative agent teammates with peer messaging.
You MUST use this skill before /pm when work is ambiguous, scope is unclear, or multiple approaches exist. Explores problem space, proposes 2-3 approaches with trade-offs, and produces an approved spec document that feeds into both issue creation (/pm) and implementation planning (/cdt). Triggers: brainstorm, explore idea, think through, design approach, what should we build, explore options, weigh approaches, compare solutions, needs help deciding between alternatives.
| name | dlc |
| description | Dev Life Cycle quality gates: run security scans, code quality checks, performance analysis, test coverage, and PR review compliance. Routes to domain-specific sub-skills or runs all checks in sequence. |
| user-invocable | true |
| allowed-tools | ["Read","Bash","Skill","AskUserQuestion"] |
| argument-hint | [--all | security | quality | perf | test | pr-check | pr-validity | git-ops] |
Automated quality gates for the development life cycle. Each sub-skill detects your project type, runs appropriate tools, and creates a GitHub issue with structured findings.
| Skill | Command | Description |
|---|---|---|
| Security | /dlc:security | Dependency audits, SAST scanning, secret detection |
| Quality | /dlc:quality | Linting, complexity analysis, duplication, dead code |
| Performance | /dlc:perf | Bundle analysis, profiling, algorithmic complexity review |
| Testing | /dlc:test | Test execution, coverage measurement, gap analysis |
| PR Review | /dlc:pr-check | Fetch PR comments, implement fixes, reply inline |
| PR Validity | /dlc:pr-validity | Detect duplicate/redundant code in PR changes |
| Git Ops | /dlc:git-ops | Branch cleanup, remote pruning, repo state verification |
/dlc → Show this overview
/dlc security → Run security scan
/dlc:security → Run security scan (alternate syntax)
/dlc --all → Run all checks in sequence
Parse the first argument:
| Argument | Route to |
|---|---|
--all | Run all sub-skills in sequence (see below) |
security | Invoke dlc:security via Skill |
quality | Invoke dlc:quality via Skill |
perf | Invoke dlc:perf via Skill |
test | Invoke dlc:test via Skill |
pr-check | Invoke dlc:pr-check via Skill |
pr-validity | Invoke dlc:pr-validity via Skill |
git-ops | Invoke dlc:git-ops via Skill |
| empty | Show overview and use AskUserQuestion to ask which check to run |
If routing to a single sub-skill, invoke it with Skill and pass any remaining arguments.
--all ModeWhen invoked with --all, invoke each sub-skill via Skill in order:
dlc:securitydlc:qualitydlc:perfdlc:testdlc:pr-check (only if on a branch with an open PR)dlc:pr-validity (only if on a branch with an open PR)After all checks complete, print a summary table:
## DLC Summary
| Check | Findings | Issue |
|-------|----------|-------|
| Security | 2 critical, 5 high | #123 |
| Quality | 0 critical, 3 medium | #124 |
| Performance | 1 high | #125 |
| Testing | 85% coverage (target: 80%) | — |
| PR Review | 3 unresolved comments | #126 |
| PR Validity | 1 high, 2 medium | #127 |
Skip any sub-skill that fails to detect its prerequisites (e.g., skip dlc:perf if no bundle config or benchmarks exist).
When invoked with no arguments, display this overview and use AskUserQuestion to ask which check to run.