gsd-quality
Apply GSD quality gates to code, security, debugging, evaluations, and interface work. Use for a structured code review, defect investigation, release audit, security pass, evaluation, or UI verification within a larger project.
- License 许可
- MIT
- 最近更新
- 2026-10-23
- Stars
- ★ 22
- Forks
- 1
01 前言 Front Matter
- name
- gsd-quality
- description
- Apply GSD quality gates to code, security, debugging, evaluations, and interface work. Use for a structured code review, defect investigation, release audit, security pass, evaluation, or UI verification within a larger project.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档references/workflows.md704 B
- 参考文档SOURCE.json353 B
03 SKILL.md 正文
GSD Quality for Locus
Adapted from Get Shit Done by Lex Christopherson under the MIT License.
- Select the narrowest quality operation that matches the risk.
- Load the relevant Superpowers skill when available: systematic debugging for defects, verification before completion for claims, TDD for behavioral changes, and review skills for feedback.
- Establish the intended behavior and evidence sources before inspecting implementation details.
- Separate confirmed findings from hypotheses; rank confirmed findings by impact.
- Fix only when the user asked for implementation. Re-run focused checks after changes and broader checks when the risk justifies them.
Read references/workflows.md for review, debug, security, evaluation, and UI gates.
Pre-flight: every reported defect must include reproducible evidence or a clearly marked uncertainty; every completion claim must cite fresh verification.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Prepare a saved implementation plan for a substantial multi-step request.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback