All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 16,413
- 684
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,233–8,256 of 16,413 skills
- Dag Cycle AnalysisGraph algorithms for detecting and resolving cycles in directed graphs and workflow definitionsVotes: 0GitHub stars: 10
- Cycle Analysis Of Directed Acyclic GraphAnalyze hierarchical DAG-like systems by separating undirected substrate from ordering metadata, then classifying diamonds, mixers, shortcuts, and hidden cycle structure. Use for workflow architecture, citation or genealogy DAG comparison, and information-flow diagnosis. NOT for ordinary cycle detection in arbitrary graphs, one-node runtime debugging, or systems with no real ordering constraint.Votes: 0GitHub stars: 10
- Cse State Of PracticeReview of Cognitive Systems Engineering applications and current practice in safety-critical domainsVotes: 0GitHub stars: 10
- Coordination Topology Architect'Choose, compare, and decompose work into the right coordination topology: dag, workflow, manager-driven team, swarm, blackboard, team-builder, or recurring loop. Use when the coordinationVotes: 0GitHub stars: 10
- Cooperative Vibe CodingCooperative vibe coding across machines — real-time collaborative development with humans and AI agents. Covers current tools (Live Share, Code With Me, Zed, Cursor multiplayer, tmux), git-based async patterns, AI agent coordination, and the aspirational future of multi-human multi-agent development. Activate on: "pair programming", "vibe coding together", "collaborative coding", "mob programming", "remote pairing", "code together", "multiplayer coding", "Live Share", "Code With Me", "ensembl...Votes: 0GitHub stars: 10
- Conway 1968 How Do Committees InventApply Conway's homomorphism principle to multi-agent system design, recognizing that agent coordination structure predetermines system architecture and capability.Votes: 0GitHub stars: 10
- Conditions For Intuitive Expertise A FaiDiagnose when intuitive judgment, agent confidence, or expert routing can be trusted by classifying environment validity, feedback quality, and task-boundary fit. Use for confidence calibration, agent routing, expertise audits, and escalation design. NOT for deterministic implementation tasks, pure syntax debugging, or domains with explicit verifiable answers.Votes: 0GitHub stars: 10
- Backend Authoritative Runtime RefactorRefactor apps so backend owns runtime truth and UI only projects snapshots. Use when tools have split authority. NOT for cosmetic UI work or new features before drift is removed.Votes: 0GitHub stars: 10
- Alphago Deep RlStrategic patterns for solving intractable problems through cascading approximation, self-improvement, and heterogeneous evaluation from DeepMind's AlphaGo systemVotes: 0GitHub stars: 10
- Agentic PatternsFundamental patterns for effective agentic behavior. Teaches decomposition, tool orchestration, error recovery, context management, quality self-assessment, and knowing when to stop. Model-agnostic principles that make any agent more effective regardless of domain. Activate on: "how should I structure this agent", "agentic workflow", "agent patterns", "multi-step task", "tool orchestration", "/agentic-patterns", "decompose this", "agent best practices", "chain of actions", "when should the ag...Votes: 0GitHub stars: 10
- N Color PickerA color picker component for selecting colors with support for multiple color modes, alpha channel, swatches, custom triggers, and native color selector integrationVotes: 0GitHub stars: 8
- Map CodebaseAnalyze codebase with parallel mapper agents to produce .planning/codebase/ documentsVotes: 0GitHub stars: 90
- Pr BranchCreate a clean PR branch by filtering out .planning/ commits — ready for code reviewVotes: 0GitHub stars: 90
- Map CodebaseAnalyze codebase with parallel mapper agents to produce .planning/codebase/ documentsVotes: 0GitHub stars: 90
- Code ReviewReview source files changed during a phase for bugs, security issues, and code quality problemsVotes: 0GitHub stars: 90
- PlanningUse when you need to plan technical solutions that are scalable, secure, and maintainable.Votes: 0GitHub stars: 3
- GitGit operations with conventional commits (cm, cp, pr, merge, finish) — scoped commits from the claim registry, finish-branch protocol with draft-default PRs + paste-ready auth fallback, and declared delivery-tail execution semanticsVotes: 0GitHub stars: 3
- Code ReviewUse when reviewing a branch, a PR, or work-in-progress changes ("review since X"), when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers edge-case scouting, pinning the review's fixed point with a merge-base diff, three-axis review (Standards vs Spec vs Security) in parallel subagents reported without reranking, the smell baselin...Votes: 0GitHub stars: 3
- Ck GraphifyBuild a queryable graph of a codebase from its AST — symbols, imports, call edges, dependency cycles — to support navigation, impact analysis, and refactoring at scale.Votes: 0GitHub stars: 3
- BrainstormUse when brainstorming software solutions, evaluating architectural approaches, debating technical decisions, or exploring feature ideas before implementation. Acts as a senior architect — challenges assumptions, presents 2-3 viable alternatives with pros/cons, and gives brutally honest feedback under YAGNI/KISS/DRY. Triggers on "/ck:brainstorm", "should we use X or Y", "how should we approach X", "is this worth the complexity", or any high-level architecture/feasibility debate. Does NOT impl...Votes: 0GitHub stars: 3
- Skill Usage InstrumenterDesign usage instrumentation for a skill library — the evidence layer answering which skills actually FIRE in practice. Covers per-invocation signals (skill name, auto-trigger vs explicit call, coarse task class — never prompt content or user identifiers), wrong-fire/correction signals, never-fires detection over a stated window, evidence tiers (host-recorded vs self-reported), and thresholds turning counts into action (fix a trigger, split, or hand an evidence package to skill-deprecation-pl...Votes: 0GitHub stars: 4
- Reviewable Diff DisciplineMANUAL-ONLY; never auto-invoke. Keep a change small, scoped, and reviewable while implementing it — one intent per branch or pull request (PR), no drive-by edits, no opportunistic refactors, no generated noise or secrets staged. Stages only the intended files by explicit path and verifies the staged set matches the declared intent before commit. Use when implementing any code change, preparing a commit or PR, or when a working diff has grown beyond its stated purpose.Votes: 0GitHub stars: 4
- Principal Code AnalystProduce a principal-level analysis of a subsystem or codebase area that connects code-level findings upward to architecture, data ownership, security posture, tenant isolation, reliability, performance, operating cost, and maintainability — and outputs an executive summary, architecture map, risk register with evidence, tradeoffs, a small-step remediation sequence, and a validation plan. Use when asked for a strategic or "principal-level" read on a subsystem, why an area is slow/fragile/expen...Votes: 0GitHub stars: 4
- Design Review FacilitatorFacilitate a technical DESIGN REVIEW — prepare it (circulate the design/spec ahead, state the decision the review must reach, invite the right reviewers including the skeptics and cross-cutting owners), structure the discussion (surface assumptions, probe the risky parts and cross-cutting concerns, weigh alternatives, keep it about the design not the person), actively elicit dissent and the strongest objection, drive to an EXPLICIT outcome (approved / approved-with-changes / needs-rework / bl...Votes: 0GitHub stars: 4