All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 16,459
- 686
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 8,593–8,616 of 16,459 skills
- Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionVotes: 0GitHub stars: 36
- Woocommerce Code ReviewReview WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.Votes: 0GitHub stars: 3
- Prompt EngineeringUse when structuring how you approach any task — select the reasoning technique that fits the task type (chain-of-thought, ReAct, few-shot, tree-of-thoughts, self-consistency, structured output) to produce production-quality work, always subordinate to verification.Votes: 0GitHub stars: 3
- Token Budget AdvisorOffers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero contro...Votes: 0GitHub stars: 3
- Css RefactorUpgrade legacy CSS to modern standards. Scans stylesheets for outdated patterns (floats, clearfix, vendor prefixes, old flexbox syntax, px media queries, @import, !important abuse) and replaces them with modern equivalents. Introduces cascade layers, extracts design tokens, and consolidates redundancy. Use when refactoring CSS, modernizing stylesheets, upgrading legacy code, removing vendor prefixes, or replacing floats with grid/flexbox.Votes: 0GitHub stars: 3
- Css DebugSystematic CSS debugging. Covers specificity analysis, inheritance tracing, computed value inspection, layout debugging (overflow, unexpected sizing, collapsing margins), CSS containment issues, z-index stacking context mapping, custom property resolution chains, and paint/layout performance diagnosis. Uses outline technique for visual debugging. Use when debugging CSS, fixing layout bugs, resolving specificity conflicts, tracing z-index issues, or diagnosing rendering performance.Votes: 0GitHub stars: 3
- Cost Aware Llm PipelineCost optimization patterns for LLM API usage — model routing by task complexity, immutable budget tracking, narrow retry logic, and prompt caching. Use when building or reviewing code that calls LLM text APIs (Claude, GPT, etc.) and spend must be routed, capped, or tracked — batch pipelines, multi-model routing, budget guardrails. Do NOT use for paid image/video render approval (that is the STOP-AND-SHOW / cost-governance-gate human-consent flow) or for choosing which model a Claude Code agen...Votes: 0GitHub stars: 3
- Context BudgetAudits Claude Code context window consumption across agents, skills, MCP servers, rules, and CLAUDE.md files — identifies bloat and redundant components and produces prioritized token-savings recommendations. Use when a session feels sluggish or degraded, after adding skills/agents/MCP servers, before adding more components, or when the user runs /context-budget or asks how much context headroom remains. Do NOT use for API billing/spend questions or for shortening a single response — this aud...Votes: 0GitHub stars: 3
- HandoffHandoff skill to assess project state and provide context for a new agent. Uses /assess logic to identify doc-code gaps, broken features, and next steps.Votes: 0GitHub stars: 6
- Extract PdfSelf-improving PDF extraction engine. Rust-native via pdf_oxide. Replaces PyMuPDF (AGPL) with MIT-licensed extraction: text, blocks, sections, tables, figures, profiling, engineering detection. Shadow-LEGO cascade for automatic quality improvement via predict-extract-verify loop.Votes: 0GitHub stars: 6
- Extract EntitiesExtract control IDs, domain phrases, taxonomy tags, and relationship data from question text. Composes /memory (ArangoDB recall to load sparta_controls vocabulary). Returns structured EntityExtractionResult that defines the shape of evidence cases, conversations, and QRA reviews before any LLM runs. Zero LLM cost — Flashtext (Aho-Corasick) + RapidFuzz (Levenshtein). NO REGEX.Votes: 0GitHub stars: 6
- DistillCompatibility shim for legacy distill callers. Forwards to /doc2qra while preserving the historical CLI interface.Votes: 0GitHub stars: 6
- Create ContextGenerate comprehensive CONTEXT.md for agent handoff. Captures current state, decisions, lessons learned, and next steps so another agent can continue with zero prior context.Votes: 0GitHub stars: 6
- Code Review RunnerDeterministic code review skill with T0 validators (best-practices-*, ruff, compile) and LLM-powered findings (codex/scillm). Scores findings by severity, keeps suggested fixes advisory, and fails closed on provider errors. Structured JSON output. Replaces raw codex exec in orchestrate T2 gate.Votes: 0GitHub stars: 6
- Classifier Lab SubagentValidate subagent reliability by running 3 concurrent classifier training loops. Each subagent runs /classifier-lab (deterministic code) and reports via JSON stream. The subagent's only job: run the skill, fix crashes, write /test-lab tests. 90% code, 10% agent. HP adjustment between rounds uses /scillm Gemini structured JSON, not agent judgment.Votes: 0GitHub stars: 6
- Best Practices SpartaBest practices for the SPARTA pipeline: data model, edge persistence, QRA generation, ArangoDB collections, and common gotchas learned the hard way.Votes: 0GitHub stars: 6
- Best Practices RustRepo-specific Rust best practices for agentic coding: thiserror + anyhow error handling, tokio async runtime, tracing for observability, clap for CLI, axum for HTTP, serde patterns, cargo workspace conventions, ownership and lifetimes, and idiomatic Rust 2024 edition patterns.Votes: 0GitHub stars: 6
- Best Practices ReportProduce evidence-bearing technical reports and report UIs without dashboard theater. Use when creating or reviewing reports, HTML/CSS report surfaces, implementation reviews, design reviews, application inventories, validation readouts, evidence ledgers, status/readiness reports, compliance/control summaries, source-of-truth audits, or issue-to-plan repair reports that must expose persona, primary object, source of truth, findings, rationale, blockers, valid actions, acceptance checks, non-cl...Votes: 0GitHub stars: 6
- Composition PatternsComposition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. These patterns make codebases easier for both humans and AI agents to work with as they scale.Votes: 0GitHub stars: 6
- Best Practices PitchdeckDeck ARCHITECTURE rules for building pitch decks from source material — measured from a real 263-slide corpus, not invented. Use when planning a deck's sections and slide sequence, when deciding which source images become slides, or when reviewing whether a generated deck is house-shaped. Exists to prevent bespoking slide architecture: sections must be DERIVED from the source document, never hardcoded in a compiler.Votes: 0GitHub stars: 6
- Best Practices Explain ProjectStandards for feature-level explainability packages: strict JSONL explainers, teleprompter notes, source/debugger stops, Excalidraw/SVG diagram bindings, common architecture interview questions, and end-of-work agent transparency.Votes: 0GitHub stars: 6
- AnvilHeavy-duty "No-Vibes" debugging and hardening orchestrator. Use this for complex, stubborn bugs where `review-code` has failed, or for "Red Teaming" (hardening) a codebase. Runs multiple agents in parallel (Thunderdome) using git worktree isolation.Votes: 0GitHub stars: 6
- Shepherd Emule PrTake an open tt-emule PR to a mergeable, ethos-compliant state. Use when asked to review a PR, address its comments, and prepare it to land — verifies every review point by build (not by trusting "addressed"), runs an emule-ethos pass for the bug classes reviewers miss, then rebases onto main locally and hands the developer a change+verification summary (with a drafted per-point comment and the exact push command) to review and push. The skill never force-pushes the author's branch itself — t...Votes: 0GitHub stars: 5
- Arch LookupLook up Tensix HW behavior across architectures specifically to inform tt-emule mock implementations. Orchestrates per-arch sage agents in parallel and aggregates results with emule-mapping context.Votes: 0GitHub stars: 5