Menu
Run the repo Rust TODO finder during sprint-end or integration review and turn every discovered TODO into a QA finding rather than deferred work.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Build a local, self-contained HTML A/B comparison viewer for two or more generated HTML variants (e.g. different template revisions, different data sets, before/after fixes), so a human can pick between panes side-by-side without any external hosting.
Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring, and template-driven findings and final quality reports.
Generate a sprint status report for the current phase. Default is --table.
Generate and triage adversarial templates, var-files, and rendering inputs against sc-compose by coordinating bounded background agents, differential and metamorphic checks, minimization, and regression-test promotion. Use when trying to break a rendering subsystem, validating a risky change, hunting parser/validator/rendering edge cases, or turning a confirmed fuzz failure into a unit or CLI test.
Team-lead drives plan hardening after the current plan state already exists in repo docs.
Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.
| name | todo-triage |
| version | 1.0.0 |
| description | Run the repo Rust TODO finder during sprint-end or integration review and turn every discovered TODO into a QA finding rather than deferred work. |
| depends_on | {"quality-management-gh":"1.x"} |
Audience: quality-mgr and team-lead.
Use this during sprint-end QA or integration review when Rust TODO hygiene must be checked explicitly.
In sc-compose, TODO comments are not an approved way to defer work.
Every discovered TODO is a policy violation until it is resolved through one of these outcomes:
fix-nowremove-nowrewrite-now-as-explanatory-commentDo not treat a TODO comment as backlog, planning authority, or silent scope deferral.
If the underlying concern is truly out of sprint scope, raise it as a QA finding and let the normal triage/planning flow capture the follow-up. Do not leave the TODO comment behind as the tracking mechanism.
Run this:
From repo root:
python3 scripts/find_todos.py
The script scans repo Rust source files only.
Output format:
file:line:tag:text
Tag rules:
TODO(P6) -> P6TODO(fix) -> fixTODO -> untaggedProduce a concise report grouped by tag:
The triage pass fails if any TODO remains unresolved at the end.