All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,951
- 623
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 97–120 of 14,951 skills
- Updating DependenciesUpdating catalog dependencies to latest minor/patch versionsVotes: 0GitHub stars: 9
- 50 Security Best PracticesUse when 安全编码最佳实践，CodeQL/Semgrep 集成 - 驱动代码安全审计、内核模块漏洞扫描。Votes: 0GitHub stars: 2
- 34 Receiving Code ReviewUse when 接收代码审查反馈 - 处理内核邮件列表 review 意见、GitHub PR review。Votes: 0GitHub stars: 2
- 33 Requesting Code ReviewUse when 请求代码审查 - 补丁提交前自查、驱动代码合并前验证。Votes: 0GitHub stars: 2
- 12 Code RefactoringUse when 驱动重构、代码结构调整 - 驱动适配新内核版本、代码模块化重构。Votes: 0GitHub stars: 2
- 10 Code ReviewUse when 补丁审查、内核补丁检查 - 内核补丁提交前审查、驱动代码质量检查。Votes: 0GitHub stars: 2
- 08 Systematic DebuggingUse when 内核 Oops/panic 分析、驱动调试 - 内核 Oops 分析、驱动 crash 定位、硬件相关 bug 排查。⭐ 核心场景Votes: 0GitHub stars: 2
- Dim ReviewReview an order's whole diff against its Build artifact, one agent per area, and return findings or the Review artifact. Use as the reviewer, when a brief names dim-review.Votes: 0GitHub stars: 5
- Dim BuildBuild an approved plan slice by slice — write test first, verify, simplify, check for correctness and pattern fit, and commit each slice through the gates, answering every finding. Use as the builder, when a brief names dim-build.Votes: 0GitHub stars: 5
- Auto AssemblerWriting Cheat Engine Auto Assembler (AA) scripts, AOB scanning (aobscanmodule), memory allocation (alloc), register preservation, code caves, assembly hooks, and enable/disable templates. Use this skill when generating, debugging, or analyzing Cheat Engine Auto Assembler injection scripts, cheat tables, and memory patches.Votes: 0GitHub stars: 42
- RefactorScan the project for refactoring opportunities, then fix them. No behavior/visual changes.Votes: 0GitHub stars: 2
- Gator GateValidate and monitor OpenShell GitHub issues and PRs using the gator:* state machine. Use when asked to triage issues/PRs for project validity, gate PRs, run gator, validate submissions, or monitor PRs toward merge readiness.Votes: 0GitHub stars: 3
- Review Github PrReview a GitHub pull request by summarizing its diff and key design decisions. Use when the user wants to review a PR, understand changes in a branch, or get a code review summary. Trigger keywords - review PR, review pull request, summarize PR, summarize diff, code review, review branch, PR summary, diff summary.Votes: 0GitHub stars: 3
- Create Github PrCreate GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.Votes: 0GitHub stars: 3
- CavecrewWhen to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer.Votes: 0GitHub stars: 9
- Weft GrowCOMMAND, not reference: Grow the program one stage at a time against a real input, seeded runs and frozen examples included. Run this when the user asks for this step by name, optionally naming the stage to grow or an example to check. The seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft GrowCOMMAND, not reference: Grow the program one stage at a time against a real input, seeded runs and frozen examples included. Run this when the user asks for this step by name, optionally naming the stage to grow or an example name to rerun. The seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft GrowCOMMAND, not reference: Grow the program one stage at a time against a real input, seeded runs and frozen examples included. Run this when the user asks for this step by name, optionally naming the stage to grow next or an example to check. The seventeen `weft-` reference skills beside it are things you read; this is a procedure you carry out.Votes: 0GitHub stars: 1,992
- Weft ConnectionsRead when the user asks about connections, API keys, sign-ins, permissions, the browser extension, human tasks, or a public URL: the connect flow door by door, what each banner means, tokens and scoping, and how HumanQuery tasks reach people.Votes: 0GitHub stars: 1,992
- Flow 5 Review CheckParanoid red-team pass over the fixes made during review, re-verifying each oneVotes: 0GitHub stars: 1,992
- Ticket System**Purpose:** Context anchor to prevent LLM loops during complex work. Colocates all artifacts. **Creating a ticket:** Run `safeword ticket new <slug>` (optionally with `--type=patch|task|feature` and `--title="..."`). The CLI mints a 6-char Crockford Base32 ID, creates the folder atomically, and writes a starter ticket.md. **Do not scan the tickets directory and pick the next ID yourself** — that races between parallel sessions and silently collides across git branches. **Location:** `.safewo...Votes: 0GitHub stars: 19
- Tdd ReviewUse when completing a TDD step and wanting a quality check. Reviews test quality after RED, implementation correctness after GREEN, and scenario completeness after REFACTOR.Votes: 0GitHub stars: 19
- Quality ReviewDeep code review with web research. Use when double-checking codeVotes: 0GitHub stars: 19
- Figure It OutExplore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstor...Votes: 0GitHub stars: 19