gsd-ns-review
quality gates | code review debug audit security eval ui
Works with
--- name: gsd-ns-review description: quality gates | code review debug audit security eval ui license: MIT --- Route to the appropriate quality / review skill based on the user's intent. `gsd-code-review-fix` was absorbed by `gsd-code-review --fix` in #2790. | User wants | Invoke | |---|---| | Review code for quality and correctness | gsd-code-review | | Auto-fix code review findings | gsd-code-review --fix | | Audit UAT / acceptance testing | gsd-audit-uat | | Security review of a phase | gsd-secure-phase | | Evaluate AI response quality | gsd-eval-review | | Review UI for design and accessibility | gsd-ui-review | | Validate phase outputs | gsd-validate-phase | | Debug a failing feature or error | gsd-debug | | Forensic investigation of a broken system | gsd-forensics | | Autonomous audit-to-fix pipeline | gsd-audit-fix | | Cross-AI peer review of plans | gsd-review | | Generate a UI design contract | gsd-ui-phase | Invoke the matched skill directly using the Skill tool.
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
