All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 15,936
- 664
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 13,705–13,728 of 15,936 skills
- Adynato GithubGitHub workflow conventions for Adynato projects. Covers creating PRs with gh CLI, writing thorough descriptions, and using stacked PRs for large deliverables. Use when creating pull requests, managing branches, or breaking down large features.Votes: 0GitHub stars: 207
- Code ReviewReview unstaged GSX code changes when the user asks for a code review, to review changes, or to check code. Applies to C, C++, CUDA, and Metal.Votes: 0GitHub stars: 207
- Clean CoderProfessional coding standards and ethics. Invoke when implementing plans, reviewing code, or when the user is frustrated. Enforces correctness over speed, honest communication, and clean outputs.Votes: 0GitHub stars: 207
- Implementation Clean CodeImplement the approved design in clean, maintainable code, keep changes aligned with requirements, and leave the codebase ready for review with unit tests and lint-clean output where practical.Votes: 0GitHub stars: 207
- Guarding Code QualityKeeps agent-generated code correct, safe, and consistent with the codebase, match existing conventions, verify behavior with a real run/test, and self-review before claiming done. Use whenever writing or editing code. Calls verifying-reasoning to confirm a fix actually fixes, and reports honestly when checks fail.Votes: 0GitHub stars: 207
- Typescript PatternsBest practices for TypeScript types, interfaces, assertions, and type safety. Use when writing or reviewing TypeScript code.Votes: 0GitHub stars: 207
- Deep ThinkPuts Claude code into a different frame of mind for better resultsVotes: 0GitHub stars: 207
- Cc Pr Review CiComprehensive TypeScript/React PR review. Outputs structured review.json consumed by a posting script that creates a GitHub Review with inline comments. Agent runs read-only; the workflow script holds write permissions.Votes: 0GitHub stars: 207
- Git CommitGenerate and create clean git commits from staged changes. Use when the user asks to commit already staged work, generate a commit message from `git diff --cached`, or run a commit workflow that infers type, scope, subject, body, and risk from the staged diff.Votes: 0GitHub stars: 207
- CsCodeStable 工作流根入口,介绍体系全貌并把诉求路由到对应 cs-* 子技能。触发:用户只输入 `cs`、说"介绍一下 codestable"、"该用哪个技能"、"不知道用哪个",或诉求还很开放未收敛。本技能只做路由不做事。Votes: 0GitHub stars: 207
- Cs Roadmap把"大到塞不进单个 feature"的需求做成完整事前规划:概设 + 接口契约 + 子 feature 拆解清单,放在 `.codestable/roadmap/{slug}/`。两种模式 new / update。触发:用户说"我想要一个 X 系统"、"帮我把这块需求拆一下"、"开一份 roadmap",或 feature-design 阶段发现需求太大。Votes: 0GitHub stars: 207
- Cs Refactor代码优化的子流程入口,处理"行为不变、结构变"的工作(结构 / 性能 / 可读性),按 scan → design → apply 分步执行每步人工放行。触发:用户说"优化一下 / 重构 / 重写 / 拆一下 / 性能不行 / 代码太长"且不夹带行为改动。不处理新需求 / bug / 跨模块架构重划。Votes: 0GitHub stars: 207
- Cs Refactor Ffrefactor 流程的超轻量通道——直接识别 1-3 条低风险优化、一次确认、原地改、跑测试自证。触发:用户说"快速重构"、"小重构"、"简单优化下 XX 函数"、"别那么多步骤",且改动在单函数 / 单组件局部、有测试可自证。Votes: 0GitHub stars: 207
- Cs Issue修 bug 的子流程入口。默认快速定位并留下 fix-note;根因不明、影响面大或用户要求完整留档时才补 report / analysis。触发:用户说"修 bug"、"有个问题"、"修复 XX"。只做路由。Votes: 0GitHub stars: 207
- Cs Feat新功能开发的子流程入口,把"加个 X 能力"从想法走到验收闭环。触发:用户说"做新功能"、"加个 X"、"实现 XX"。只做路由,根据已有产物决定走 brainstorm / design / fastforward / implement / acceptance。不处理 bug。Votes: 0GitHub stars: 207
- Cs Feat Implfeature 流程阶段 2——按 {slug}-checklist.yaml 里 design 切好的 paradigm 维度 steps 推进,每步具体改哪个文件由 implement 自决,写完用统一格式汇报。触发:用户说"方案确认了开始实现"、"按方案写代码"、"开工"。前提是 design 已 approved 且有 checklist。遇到方案外情况要回方案谈不要硬冲。Votes: 0GitHub stars: 207
- Cs Feat Designfeature 流程阶段 1——为新功能起草 {slug}-design.md 作为后续实现和验收的唯一输入,拍板后抽出 checklist。触发:用户说"开始设计方案"、"写 design doc"、"准备实现 XX",前提是已知道做什么、为谁、怎么算成功。Votes: 0GitHub stars: 207
- Cs Feat Acceptfeature 流程阶段 3——验收闭环:对照 design 核实现 + 回写 architecture / requirement / roadmap,最后产出 {slug}-acceptance.md。触发:用户说"功能写完了验收一下"、"做最后检查"、"准备 merge"、"出验收报告"。前置依赖 cs-feat-impl 完成。Votes: 0GitHub stars: 207
- Cs Doc Sweep手动触发的 CodeStable 文档熵清理工作流。用于用户明确要求"清理旧设计文档"、"做文档熵检查"、"分析 features/issues/refactors 哪些还有效"、"这个新 feature 推翻了旧方案"、"全项目扫一遍旧 spec 是否重复/过期"时。不会由 feature-accept、issue-fix、refactor 等工作流主动触发。Votes: 0GitHub stars: 207
- Cs Brainstorm想法还模糊时的讨论入口,做分诊后路由到 feature-design / feature-brainstorm / roadmap。AI 是思考伙伴不是记录员。触发:用户说"有个想法还没想清楚"、"先 brainstorm 一下"、"聊一聊这块"、"方向还在摇摆"。不处理 bug 和重构。Votes: 0GitHub stars: 207
- Cs Audit系统审计——从代码中主动发现 bug 隐患、安全漏洞、性能问题、可维护性债务和架构偏离,产出批量发现清单。触发:用户说"审查系统"、"审计代码"、"扫描问题"、"找找 bug"、"有什么可以优化的"。Votes: 0GitHub stars: 207
- Cs Arch维护 `.codestable/architecture/` 这份只记现状的系统地图,三种模式 update / check / backfill。触发:用户说"刷新 architecture"、"做架构检查"、"补这个模块的架构文档"、"方案和代码对得上吗",或 feature 阶段需要先做架构动作。不写未来规划(走 cs-roadmap)。Votes: 0GitHub stars: 207
- Run TestsExecute tests with coverage analysis using bmad-commands, identify coverage gaps, and suggest missing tests. This skill should be used for test execution and quality validation.Votes: 0GitHub stars: 207
- Quality GateSynthesize all quality assessments (risk, test-design, traceability, NFR) into evidence-based gate decision (PASS/CONCERNS/FAIL/WAIVED) with comprehensive rationale. Generates both YAML (CI/CD) and Markdown (human review) reports with action items. Use during final quality review to make go/no-go deployment decisions based on comprehensive quality evidence.Votes: 0GitHub stars: 207