All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 15,938
- 665
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 1,057–1,080 of 15,938 skills
- Structuring Shared Agent StateWrite the state snapshot every agent decision reads, with goal, evidence and gaps, and write each action's real result back before the next call.Votes: 0GitHub stars: 2
- Designing Routing And Ranking PoliciesUse typed decision calls to choose workers, tools, models and next steps, and to score sources, while code enforces the result.Votes: 0GitHub stars: 2
- Checking Post Action ResultsConfirm an agent action changed the world as intended by comparing a pre-written expected outcome with fresh evidence gathered after it ran.Votes: 0GitHub stars: 2
- Calibrating Confidence Thresholds And Escalation PathsTurn a decision model's confidence scores into measured thresholds that decide when an agent acts, falls back, or escalates.Votes: 0GitHub stars: 2
- Building Idealized InfluenceEarn trust by modeling the standards you expect, putting the group's needs first, and acting consistently with shared values.Votes: 0GitHub stars: 2
- Applying Loop Termination And Continuation RulesWrite explicit done, failure, budget, stall and approval rules before an agent loop runs, then apply them after every iteration.Votes: 0GitHub stars: 2
- AutopilotOrchestrate unattended resolution of open GitHub issues - triage by complexity, dispatch parallel worker agents into isolated worktrees, review their diffs, open PRs, and monitor CI and CodeRabbit until green. Use when asked to work through open issues autonomously or put Claude on auto-pilot.Votes: 0GitHub stars: 16
- RoadmapAdd or update an entry in docs/roadmap.md. Enforces the standard structure (Status / Complexity / Value / Description / Benefits / Prerequisites / Dependencies / Related) and category placement.Votes: 0GitHub stars: 19
- TerraformTerraform best practices: state, security, modules, workflow, testing, tooling. Use when writing or reviewing Terraform code.Votes: 0GitHub stars: 54
- LaravelLaravel 13 best practices: architecture, Eloquent, security, queues, testing, tooling. PHP 8.3+. Use when writing or reviewing Laravel applications.Votes: 0GitHub stars: 54
- Karpathy GuidelinesBehavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.Votes: 0GitHub stars: 54
- Multi Agent Task OrchestratorA production-tested pattern for coordinating multiple AI agents through a single orchestrator. Instead of letting agents work independently (and conflict), one orchestrator decomposes tasks, routes them to specialists, prevents duplicate work, and verifies results before marking anything done.Votes: 0GitHub stars: 2
- Workers Best PracticesReviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.Votes: 0GitHub stars: 2
- Systems Coding StyleWrite and review C, C++, Rust, and low-level systems code with a small, idiomatic, professional style. Use for implementation, refactoring, or review where unnecessary abstraction, allocation, cleverness, or explanatory comments should be avoided.Votes: 0GitHub stars: 2
- Modern CppWrite, review, and modernize C++ with repository-compatible language features, precise interfaces, RAII, explicit ownership, safe concurrency, and measured hardening. Use for C++ implementation, refactoring, API design, or safety review; do not use for pure C or build-system-only work.Votes: 0GitHub stars: 2
- Code StandardsGovern implementation, bug fixes, and refactors from repository orientation through scoped research, planning, evidence-led tests, implementation, review, verification, and handoff. Use for any code change; combine it with the relevant language skill for C, C++, Rust, assembly, or another stack.Votes: 0GitHub stars: 2
- Code Quality Review[Code Quality] Use when evaluating received review feedback, reviewing named code on request, or verifying a completion claim. Current diffs: changes-review; rationale: why-review.Votes: 0GitHub stars: 3
- Code Quality Review[Code Quality] Use when evaluating received review feedback, reviewing named code on request, or verifying a completion claim. Current diffs: changes-review; rationale: why-review.Votes: 0GitHub stars: 3
- Praxis WatchUse when the user wants one background session watching both the PR review-request channel and their assigned tickets — "lance la veille", "/loop /praxis-watch", "surveille les PR et mes tickets". One pass per invocation, designed for /loop. Do NOT use for a single watcher on demand (/praxis-watch-prs, /praxis-watch-tickets).Votes: 0GitHub stars: 3
- Praxis TddUse when implementing any feature or bugfix with strict baby-steps TDD - enforces minimal code and mandatory checkpointsVotes: 0GitHub stars: 3
- Praxis ReviewUniversal code review - auto-detects scope from git changes, spec, commit, or brief. Use after completing tasks, implementing major features, before merging, when stuck (fresh perspective), before refactoring (baseline check), or after fixing complex bugs.Votes: 0GitHub stars: 3
- Jev Model RouterUse `jev_route_model` when more than one available model could perform the task and the choice materially affects quality, cost, or latency.Votes: 0GitHub stars: 17
- Ponytail ReviewCode review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.Votes: 0GitHub stars: 17
- Plan ArbiterUse when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.Votes: 0GitHub stars: 17