Loading...
Loading...
Found 794 Skills
Code review practices with technical rigor and verification gates. Practices: receiving feedback, requesting reviews, verification gates. Capabilities: technical evaluation, evidence-based claims, PR review, subagent-driven review, completion verification. Actions: review, evaluate, verify, validate code changes. Keywords: code review, PR review, pull request, technical feedback, review feedback, completion claim, verification, evidence-based, code quality, review request, technical rigor, subagent review, code-reviewer, review gate, merge criteria. Use when: receiving code review feedback, completing major features, making completion claims, requesting systematic reviews, validating before merge, preventing false completion claims.
Update Knowledge Base — Execute doc-updater, code-reviewer, and learn-eval in sequence to solidify the changes from this session into documents and knowledge.
Emulate supported AI code-review GitHub Actions locally and print a terminal-only review from portable skill instructions. Use when running /review-action or checking local PR-review feedback before publishing.
Refresh stale learning docs and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, replacing, or deleting the drifted ones. Trigger this skill when the user asks to refresh, audit, sweep, clean up, or consolidate stale docs in docs/solutions/ (phrases like "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", "consolidate overlapping docs", "compound refresh", "/ce-compound-refresh"), or when ce-compound has just captured a new learning and flagged a specific older doc in docs/solutions/ as now inaccurate or superseded — invoke with the narrow scope hint ce-compound provides. Also trigger when the user points at a specific learning or pattern doc under docs/solutions/ and calls it stale, outdated, overlapping, or drifted. Do not trigger for general refactor, migration, debugging, or code-review work unless the user has explicitly directed attention to docs/solutions/ itself.
Review Skill definition quality. Use when user asks to "review skill", "check skill quality", "validate skill", "lint skill", "review my skill", or wants to check if a Skill follows best practices. For execution trace analysis, use when user explicitly mentions "analyze execution", "review trace", or "evaluate execution process". Do NOT use for runtime debugging (use agent-debug skill), code review (use code-review skill), or general file validation.
Make AI-generated writing read as human-written, in fiction and in professional prose. Repairs the narrative architecture of fiction and stories (based on StoryScope, arXiv:2604.03136); routes professional text through domain rules for release notes, announcements, PR and issue replies, code-review comments, incident postmortems, tickets, work orders, technical articles, and blog posts. Four operations - write, review (diagnose AI tells without editing), refactor (minimal in-place edits), recreate (full rewrite). Use when asked to humanize, de-AI, unslop, or strip AI flavor from any text; when writing or revising any of these document types; or whenever output must not read as machine-written.
You MUST use this when code-review findings, PR comments, CI review output, or reviewer suggestions need technical validation before any fix or disposition, including feedback from human reviewers, subagents, GitHub, static-analysis tools, or external review systems.
Run independent code-review agents and synthesize verified findings.
Create, audit, or trim AGENTS.md and its harness mirrors (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, .cursor/rules) so build/test commands stay accurate and the file stays under each harness's size cap. Use when the user says "create AGENTS.md", "audit AGENTS.md", "trim AGENTS.md", "AGENTS.md is stale", "CLAUDE.md drift", "agent instructions hygiene", or invokes /agents-md. Covers nested AGENTS.md for monorepo packages, nearest-file precedence, and the bundled scripts/agents_md_check.py measurement script. Do NOT use for `.github/copilot-instructions.md` authoring or Copilot code-review configuration — that is /github-copilot-repo-instructions. Do NOT use for personal, per-user, or machine-global instruction files (`~/.claude/CLAUDE.md`, personal Copilot instructions) — those are out of scope for this repository-scoped skill.
Implement a piece of work based on a PRD or set of issues.
Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
Implement a specification in code.