代码质量与审查 Skill

「代码质量与审查」分类共 235 个 Skill，按仓库 star 排序。分类自动生成，仅供参考。

全部 AI 与智能体1707 文档与办公662 前端开发572 测试528 项目与协作342 数据库与数据300 DevOps 与云291 科研289 代码质量与审查235 安全225 浏览器自动化217

ml-training-recipes

OpenRaiser/NanoResearch1.3k

ml-training-recipes

Battle-tested PyTorch training recipes for all domains — LLMs, vision, diffusion, medical imaging, protein/drug discovery, spatial omics, genomics. Covers training loops, optimizer selection (AdamW, Muon), LR scheduling, mixed precision, debugging, and systematic experimentation. Use when training or fine-tuning neural networks, debugging loss spikes or OOM, choosing architectures, or optimizing GPU throughput.

oma-architecture

first-fluke/oh-my-agent1.3k

oma-architecture

Evaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.

anti-entropy-governance

GanyuanRan/Aegis1.3k

anti-entropy-governance

Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.

communicating-concisely

GanyuanRan/Aegis1.3k

communicating-concisely

Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.

dispatching-parallel-agents

GanyuanRan/Aegis1.3k

dispatching-parallel-agents

Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.

establishing-project-context

GanyuanRan/Aegis1.3k

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

executing-plans

GanyuanRan/Aegis1.3k

executing-plans

Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.

finishing-a-development-branch

GanyuanRan/Aegis1.3k

finishing-a-development-branch

Use when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly requests merge, PR, or branch lifecycle handling.

first-principles-review

GanyuanRan/Aegis1.3k

first-principles-review

Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.

goal-framing

GanyuanRan/Aegis1.3k

goal-framing

Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.

long-task-continuation

GanyuanRan/Aegis1.3k

long-task-continuation

Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.

receiving-code-review

GanyuanRan/Aegis1.3k

receiving-code-review

Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.

recording-architecture-decisions

GanyuanRan/Aegis1.3k

recording-architecture-decisions

Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.

requesting-code-review

GanyuanRan/Aegis1.3k

requesting-code-review

Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.

subagent-driven-development

GanyuanRan/Aegis1.3k

subagent-driven-development

Use when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.

update-aegis

GanyuanRan/Aegis1.3k

update-aegis

Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.

using-aegis

GanyuanRan/Aegis1.3k

using-aegis

Use when starting a turn or checking Aegis skill routing.

using-git-worktrees

GanyuanRan/Aegis1.3k

using-git-worktrees

Use when a coding task needs a concurrent checkout, unrelated dirty state blocks safe branch switching, or the user or repository explicitly requires a worktree.

verification-before-completion

GanyuanRan/Aegis1.3k

verification-before-completion

Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.

visual-flow-gif

AI-Builder-Club/skills1.3k

visual-flow-gif

Create animated flow diagrams from articles, workflow notes, architecture sketches, or process descriptions using a JSON specification and a local Python/Pillow renderer. Use when the user wants to turn source material into a static PNG + animated GIF diagram.

reddit-search-api

lignertys/reddit-research-skills1.3k

reddit-search-api

Pure API reference for reddapi.dev - authentication, all endpoints (vector search, semantic search, trends, subreddit lookup), request parameters, response schemas, and error codes, with no research-workflow framing. Use when the user wants raw endpoint documentation, is debugging a reddapi.dev integration, needs exact request/response field names, or asks for 'reddapi API reference', 'reddapi.dev endpoints', or 'reddapi error codes'. For guided research workflows and query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads.

code-structure

michaelshimeles/skills1.3k

code-structure

Use when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across domain flows. Use when adding new features that share mechanics with existing ones.

greploop

michaelshimeles/skills1.3k

greploop

Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review, and repeats. Use when the user wants to fully optimize a PR/MR/CL against Greptile's code review standards.

greploop-apps

michaelshimeles/skills1.3k

greploop-apps

Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Identical to greploop, but triggers reviews by tagging @greptile-apps, which bypasses Greptile's file-count limit on huge PRs that the plain @greptile mention refuses to review. Use when the user wants to fully optimize a large PR/MR/CL against Greptile's code review standards.