all publishers

alexandrbasis

@alexandrbasis source repo

160 published skills · page 1 of 2

  1. ▌
    Ct 4 · alexandrbasis bundle
    Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
    12 repo stars
  2. ▌
    Nf 4 · alexandrbasis bundle
    Runs an in-depth feature-discovery interview that explores, challenges, and documents a new feature before planning. Use when asked to 'detail a feature', 'explore a new feature', 'feature discovery', 'interview about feature', 'spec out a feature', 'design a feature', 'think through a feature', 'deep dive on a feature', 'discover [feature-name]', or 'what should we consider for [feature]'. NOT for quick brainstorming (/brainstorm), PRD/JTBD docs (/product), or implementation tasks (/ct).
    12 repo stars
  3. ▌
    Ph 4 · alexandrbasis
    Prepare session handoff for continuation in a new conversation. Use when 'prepare handoff', 'save progress', 'session handoff', 'I need to stop', 'prepare for next session', 'hand off', 'write handoff', or when the user wants to pause mid-implementation and resume later in a fresh context window.
    12 repo stars
  4. ▌
    QA 4 · alexandrbasis
    Interactive QA session where the user reports bugs conversationally and the agent files them as tracker issues (GitHub or Linear) one by one or as a dependency-linked breakdown. Explores the codebase in the background for context and domain language. Use when user wants to "do QA", "report bugs", "file issues from a QA pass", or runs through multiple problems at once. NOT for single-bug triage (use /triage-issue) or interactive debug (/dbg).
    12 repo stars
  5. ▌
    Si 4 · alexandrbasis bundle
    Implement or resume a task from its existing plan and acceptance criteria, with behavior-first tests and recorded verification. Use for requested implementation; unresolved discovery belongs to /nf, planning to /ct, and independent review to /sr.
    12 repo stars
  6. ▌
    Sr 4 · alexandrbasis bundle
    Use when asked to review code before merge or review a PR, branch, commit range, task path, or current working tree. Trigger on requests like 'review PR', 'review my changes', 'review this branch', 'is this ready to merge', or other pre-merge review requests. Supports task/spec-aware review when task docs exist. NOT for addressing review comments (use /prc).
    12 repo stars
  7. ▌
    Vp 4 · alexandrbasis bundle
    Create interactive visual prototype playground for user approval before technical decomposition. Use when asked to 'create prototype', 'visual mockup', 'preview design', 'design playground', 'show me the feature', 'what would this look like', 'mockup the UI', 'visualize the architecture', 'preview before building', 'let me see the design', or anytime the user wants to see or approve a visual representation of a feature before coding begins. Also trigger when /nf discovery is complete and the user says 'looks good, let's see it', 'now show me', or 'visualize this'. NOT for brainstorming (use /brainstorm), NOT for feature discovery (use /nf), NOT for implementation tasks (use /ct), NOT for quick one-off diagrams (use /generate-web-diagram).
    12 repo stars
  8. ▌
    Dbg 4 · alexandrbasis
    Debug mode with runtime evidence and instrumentation. Use when asked to 'debug this', 'find the bug', 'troubleshoot', 'why is this broken', 'investigate runtime issue', 'it's not working', 'getting an error', 'this crashes', 'unexpected behavior', or when the user pastes an error message or stack trace and wants to find the root cause. Also trigger when the user describes behavior that differs from expectations in a running app. NOT for static code analysis without reproduction (use /code-analysis). NOT for CI pipeline failures (use /fci).
    12 repo stars
  9. ▌
    Design Exploration 4 · alexandrbasis bundle
    Explore codebase and design approaches before implementation. Use when asked 'explore the design', 'how would this fit', 'design exploration', 'what patterns exist for', 'how is X implemented', or when another skill (brainstorm, nf) needs codebase context to ground a design proposal. NOT for code review (use /sr), NOT for static analysis (use /code-analysis).
    12 repo stars
  10. ▌
    Review Conventions 4 · alexandrbasis
    Internal reference skill — shared conventions for all code review agents. Not user-invocable.
    12 repo stars
  11. ▌
    Ubiquitous Language 4 · alexandrbasis
    Build or update a DDD-style ubiquitous language glossary when the user explicitly asks to define domain terms, build/update the project glossary, or harden terminology. For /nf, /product, or /ct context-reading calls, load and report the glossary; for authorized post-grill updates, merge and write it. Do not write for a load-only or explanatory request. NOT for architectural vocabulary (use /architecture-language).
    12 repo stars
  12. ▌
    Architecture Language 4 · alexandrbasis bundle
    Canonical architectural vocabulary — module, interface, seam, adapter, depth, leverage, locality. Use when reviewing architecture, deepening shallow modules, designing interfaces, or evaluating refactor candidates. NOT a domain glossary (use /ubiquitous-language for that). Use as a standalone skill only when explicitly requested by the user; automatic selection is not authorization. Portable clients may not enforce this host-level restriction.
    12 repo stars
  13. ▌
    Improve Codebase Architecture 4 · alexandrbasis bundle
    Explore a codebase for architectural deepening opportunities: refactors that turn shallow modules into deeper ones with better testability and locality. Use when the user explicitly asks for architecture improvement, refactoring opportunities, or coupled-module analysis. Do not use for pre-merge review (use /sr) or spec gaps (use /ct). Read-only; it does not write code.
    12 repo stars
  14. ▌
    Codex CLI 4 · alexandrbasis bundle
    Run OpenAI Codex CLI for one-shot cross-AI code review or approach validation. Invoke ONLY when the user explicitly asks ('second opinion', 'codex review', 'ask codex', 'run codex', 'cross-AI check'), or when another skill passes an explicit instruction to delegate to codex. Do not invoke proactively on general review requests. Not for interactive conversations.
    12 repo stars
  15. ▌
    Brainstorm 4 · alexandrbasis
    Compare options and clarify a decision through a collaborative brainstorming session. Use when asked to 'brainstorm', 'let's brainstorm', 'explore ideas', 'think through', 'brainstorm about [topic]', 'what are our options for', 'let's think about', 'pros and cons of', 'help me decide', or 'weigh the options'. NOT for feature discovery (use /nf), NOT for PRD/JTBD docs (use /product), NOT for deep research (use /deep-research), NOT for pre-implementation design (auto-triggered by design-exploration skill).
    12 repo stars
  16. ▌
    Cursor CLI 4 · alexandrbasis bundle
    Run Cursor CLI for one-shot cross-AI code review when a Cursor perspective is explicitly wanted. Invoke ONLY when the user asks ('cursor review', 'ask cursor', 'run cursor'), or another skill explicitly delegates to Cursor. Do not invoke it implicitly for a generic review. Not for interactive conversations.
    12 repo stars
  17. ▌
    Dev Server 4 · alexandrbasis
    Start any project's dev server and monitor it for errors in real-time. Universal — works with Node.js (Next.js, Vite, Remix, Astro, SvelteKit, Nuxt, Angular, Gatsby, Expo), Python (Django, Flask, FastAPI, Uvicorn), Ruby (Rails, Sinatra), Go, Rust (Cargo), Java (Spring Boot, Gradle, Maven), PHP (Laravel, Symfony), Elixir (Phoenix), and Docker Compose. Auto-detects the stack and package manager from project files. Uses the Monitor tool to stream only errors, warnings, and crashes — not routine request logs. Use this skill whenever the user says "start dev server", "run dev", "start the app", "launch the server", "npm run dev", "cargo run", "python manage.py runserver", "rails server", "go run", or anything that implies starting a local development server. Also trigger when the user asks to "monitor the server", "watch the build", "check for errors while I work", or simply "dev".
    12 repo stars
  18. ▌
    Triage Issue 4 · alexandrbasis
    Investigate a reported bug, find its root cause, and file a tracker issue (GitHub or Linear) with a TDD-based fix plan. Mostly hands-off — minimize questions to the user. Does NOT apply the fix. Use when user reports a bug and wants it tracked, mentions "triage", "file an issue", or "investigate and plan a fix". NOT for interactive debugging (use /dbg) or batch QA sessions (use /qa).
    12 repo stars
  19. ▌
    Update Setup 4 · alexandrbasis bundle
    Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
    12 repo stars
  20. ▌
    Code Analysis 4 · alexandrbasis bundle
    Analyze the structure and quality of the current codebase with evidence-backed metrics, patterns, and recommendations. Use for an explicit code audit, architecture assessment, codebase overview, hotspot/complexity question, module-dependency analysis, or pre-implementation exploration. Do not use for pre-merge review (use /sr), runtime debugging (use /dbg), or external-technology research (use /deep-research).
    12 repo stars
  21. ▌
    Deep Research 4 · alexandrbasis
    Research an external, current, niche, or unfamiliar technical topic with cited evidence. Use for explicit research, comparisons, technology evaluation, migration/dependency decisions, or questions whose answer depends on sources outside the local codebase. Do not use for quick brainstorming (use /brainstorm), feature discovery (use /nf), or static local code analysis (use /code-analysis).
    12 repo stars
  22. ▌
    Git Guardrails 4 · alexandrbasis
    Inspect, install, customize, or troubleshoot the harness-level git safety hook that blocks dangerous git operations (push, branch -D, checkout .) before they execute. Use when the user wants to change which git commands are blocked, verify the guard is wired up, or set it up after a fresh clone. Use as a standalone skill only when explicitly requested by the user; automatic selection is not authorization. Portable clients may not enforce this host-level restriction.
    12 repo stars
  23. ▌
    Antigravity CLI 4 · alexandrbasis bundle
    Run Google Antigravity CLI (agy) for web-grounded research, cross-AI review, or validation when those capabilities are explicitly needed or another skill delegates to agy. One-shot only; do not select it for an ordinary review without an explicit provider choice.
    12 repo stars
  24. ▌
    Parallelization 4 · alexandrbasis
    Parallelize genuinely independent implementation items when /si or the user asks for parallel work. Use /si directly for one item, dependent work, shared files, or shared mutable state.
    12 repo stars
  25. ▌
    Coding Conventions 4 · alexandrbasis
    Internal reference skill — coding standards and patterns for developer agents. Not user-invocable.
    12 repo stars
  26. ▌
    Fci 4 · alexandrbasis
    Fix CI pipeline failures blocking PR merge. Use when CI checks fail, 'pipeline broken', 'build failing', 'fix CI', or 'checks not passing'. NOT for debugging runtime bugs (use /dbg), NOT for code review (use /sr). Use as a standalone skill only when explicitly requested by the user; automatic selection is not authorization. Portable clients may not enforce this host-level restriction.
    12 repo stars
  27. ▌
    Prc 4 · alexandrbasis
    Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si).
    12 repo stars
  28. ▌
    Rip 4 · alexandrbasis
    Review a technical implementation plan for business-value alignment and scope fit. Use when asked to 'review my plan', 'walk through implementation', 'check plan against PRD', 'review technical decomposition', or 'is my plan aligned with requirements'. NOT for code review (use /sr), NOT for creating tasks (use /ct), NOT for static code analysis (use /code-analysis).
    12 repo stars
  29. ▌
    Sbs 4 · alexandrbasis
    Interactive teaching guide for learning while working. Use when asked to 'teach me', 'walk me through', 'explain step by step', 'guide me through', 'show me how', 'learn while doing', 'I want to understand', 'help me learn', 'can you explain how', 'what does this do and why', or when the user expresses desire to understand a topic deeply rather than just get a quick answer. Also trigger when the user wants to learn a new tool, library, pattern, or workflow hands-on — even if they don't use the word "teach". NOT for open-ended brainstorming (use /brainstorm), NOT for quick one-off explanations (just answer directly), NOT for debugging (use /dbg).
    12 repo stars
  30. ▌
    Tdd 4 · alexandrbasis bundle
    Test-driven development with red-green-refactor loop using vertical slices. Use when building features or fixing bugs with TDD, when /si or /si-quick needs canonical TDD discipline, when user mentions "red-green-refactor", "tracer bullets", "test-first", or asks for integration-style tests. Forbids horizontal slicing (all tests then all implementation). Use as a standalone skill only when explicitly requested by the user; automatic selection is not authorization. Portable clients may not enforce this host-level restriction.
    12 repo stars
  31. ▌
    Udoc 4 · alexandrbasis
    Update documentation for a completed implementation and, when the repository uses one or the user requests it, update its changelog. NOT for creating new product docs (use /product).
    12 repo stars
  32. ▌
    Quick 4 · alexandrbasis
    Apply a small change with known scope or a diagnosed bug fix using a compact task record. Use for quick fixes, configuration edits and bounded refactors; use /ct when the work needs unresolved design or coordinated implementation planning.
    12 repo stars
  33. ▌
    Setup 4 · alexandrbasis bundle
    Configure claudops for a specific repository after copying the workflow or installing the plugin. Use for first setup, requested reconfiguration, or unresolved project placeholders in claudops files.
    12 repo stars
  34. ▌
    Analyze 4 · alexandrbasis
    Compare a task's discovery or product requirements with its tech decomposition and report traceability gaps. Use when asked to 'analyze consistency', 'check alignment', 'verify spec matches plan', 'traceability check', 'spec drift', 'are my docs aligned', or after /ct completes to verify the plan covers the requirements. `/ct` may invoke this check when traceability is material; otherwise it remains an explicit read-only command. NOT for code review (use /sr), NOT for code analysis (use /code-analysis), NOT for debugging (use /dbg).
    12 repo stars
  35. ▌
    Product 4 · alexandrbasis
    Create a JTBD or PRD that records the user problem, evidence, scope, and measurable outcome through an interactive product interview. Use when asked to 'create JTBD', 'write a PRD', 'product requirements', 'jobs to be done', 'product documentation', 'product spec', or when a feature needs formal product-level documentation before technical planning. Conducts research, interviews, and pressure-tests the product thinking before writing. NOT for technical decomposition (use /ct), NOT for feature discovery (use /nf).
    12 repo stars
  36. ▌
    Finisher 4 · alexandrbasis
    Ship an existing implementation by committing local changes, pushing an open PR, waiting for green CI, and merging it. Use when the user explicitly asks to 'merge the PR', 'ship it', 'merge and close', 'commit push merge', 'finalize this PR', or 'land this branch'. Do not trigger on generic end-of-work language without a resolved PR or branch destination. This flow works with or without a task directory; phase handoff details live in Gate 3. NOT for opening a new PR (use plain `gh pr create`). NOT for addressing review comments (use /prc). NOT for preparing a session handoff to a fresh context (use /ph).
    12 repo stars
  37. ▌
    Grill Me 4 · alexandrbasis
    Use when a plan, design, or discovery document needs stress-testing for hidden assumptions, scope gaps, unresolved branches, or ambiguous wording; also when the user explicitly says "grill me".
    12 repo stars
  38. ▌
    Zoom Out 4 · alexandrbasis
    Step up one layer of abstraction and produce a map of the relevant modules and their callers — used when you (or the agent) are stuck in one file and losing the bigger picture. Use when user says "zoom out", "give me a map", "I'm lost in this code", or "what calls this". Use as a standalone skill only when explicitly requested by the user; automatic selection is not authorization. Portable clients may not enforce this host-level restriction.
    12 repo stars
  39. ▌
    Blueprint 4 · alexandrbasis
    Turn a one-line objective into a bounded staged implementation plan with cold-start briefs. Use when asked to 'blueprint', 'multi-session plan', 'long-term plan', 'construction plan', 'break into sessions', 'plan across sessions', 'multi-step project plan', 'session plan', or when work needs staged handoffs. Produces a plan where each step can be resumed independently by a fresh agent with no prior context.
    12 repo stars
  40. ▌
    Cc Linear 4 · alexandrbasis bundle
    Execute Linear operations via direct GraphQL API — create issues, update status/priority/title, add comments, search tasks, manage labels, assign work, and link PRs. Use this skill when the user mentions Linear explicitly, or references a Linear-style identifier (uppercase team prefix + dash + number, e.g. ENG-123, OPS-7; the project's team key is in $LINEAR_TEAM_KEY). Trigger on phrases like "create a Linear ticket/issue", "move TEAM-X to done/in progress/review", "update the Linear task status", "close the Linear issue", "what's in our Linear backlog", "assign this Linear issue to", "my Linear issues", or any project management operation targeting Linear. Also trigger when other skills (ct, si, sr) need to sync state with Linear. Do not trigger on ambiguous "create an issue" when the user clearly means a GitHub Issue (repo context, `gh issue` commands, issues.md), unless they also reference Linear.
    12 repo stars
  41. ▌
    Ct 3 · alexandrbasis bundle
    Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
    12 repo stars
  42. ▌
    Nf 3 · alexandrbasis bundle
    Runs an in-depth feature-discovery interview that explores, challenges, and documents a new feature before planning. Use when asked to 'detail a feature', 'explore a new feature', 'feature discovery', 'interview about feature', 'spec out a feature', 'design a feature', 'think through a feature', 'deep dive on a feature', 'discover [feature-name]', or 'what should we consider for [feature]'. NOT for quick brainstorming (/brainstorm), PRD/JTBD docs (/product), or implementation tasks (/ct).
    12 repo stars
  43. ▌
    Ph 3 · alexandrbasis
    Prepare session handoff for continuation in a new conversation. Use when 'prepare handoff', 'save progress', 'session handoff', 'I need to stop', 'prepare for next session', 'hand off', 'write handoff', or when the user wants to pause mid-implementation and resume later in a fresh context window.
    12 repo stars
  44. ▌
    QA 3 · alexandrbasis
    Interactive QA session where the user reports bugs conversationally and the agent files them as tracker issues (GitHub or Linear) one by one or as a dependency-linked breakdown. Explores the codebase in the background for context and domain language. Use when user wants to "do QA", "report bugs", "file issues from a QA pass", or runs through multiple problems at once. NOT for single-bug triage (use /triage-issue) or interactive debug (/dbg).
    12 repo stars
  45. ▌
    Si 3 · alexandrbasis bundle
    Implement or resume a task from its existing plan and acceptance criteria, with behavior-first tests and recorded verification. Use for requested implementation; unresolved discovery belongs to /nf, planning to /ct, and independent review to /sr.
    12 repo stars
  46. ▌
    Sr 3 · alexandrbasis bundle
    Use when asked to review code before merge or review a PR, branch, commit range, task path, or current working tree. Trigger on requests like 'review PR', 'review my changes', 'review this branch', 'is this ready to merge', or other pre-merge review requests. Supports task/spec-aware review when task docs exist. NOT for addressing review comments (use /prc).
    12 repo stars
  47. ▌
    Vp 3 · alexandrbasis bundle
    Create interactive visual prototype playground for user approval before technical decomposition. Use when asked to 'create prototype', 'visual mockup', 'preview design', 'design playground', 'show me the feature', 'what would this look like', 'mockup the UI', 'visualize the architecture', 'preview before building', 'let me see the design', or anytime the user wants to see or approve a visual representation of a feature before coding begins. Also trigger when /nf discovery is complete and the user says 'looks good, let's see it', 'now show me', or 'visualize this'. NOT for brainstorming (use /brainstorm), NOT for feature discovery (use /nf), NOT for implementation tasks (use /ct), NOT for quick one-off diagrams (use /generate-web-diagram).
    12 repo stars
  48. ▌
    Dbg 3 · alexandrbasis
    Debug mode with runtime evidence and instrumentation. Use when asked to 'debug this', 'find the bug', 'troubleshoot', 'why is this broken', 'investigate runtime issue', 'it's not working', 'getting an error', 'this crashes', 'unexpected behavior', or when the user pastes an error message or stack trace and wants to find the root cause. Also trigger when the user describes behavior that differs from expectations in a running app. NOT for static code analysis without reproduction (use /code-analysis). NOT for CI pipeline failures (use /fci).
    12 repo stars
  49. ▌
    Fci 3 · alexandrbasis
    Fix CI pipeline failures blocking PR merge. Use when CI checks fail, 'pipeline broken', 'build failing', 'fix CI', or 'checks not passing'. NOT for debugging runtime bugs (use /dbg), NOT for code review (use /sr).
    12 repo stars
  50. ▌
    Prc 3 · alexandrbasis
    Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si).
    12 repo stars
  51. ▌
    Rip 3 · alexandrbasis
    Review a technical implementation plan for business-value alignment and scope fit. Use when asked to 'review my plan', 'walk through implementation', 'check plan against PRD', 'review technical decomposition', or 'is my plan aligned with requirements'. NOT for code review (use /sr), NOT for creating tasks (use /ct), NOT for static code analysis (use /code-analysis).
    12 repo stars
  52. ▌
    Sbs 3 · alexandrbasis
    Interactive teaching guide for learning while working. Use when asked to 'teach me', 'walk me through', 'explain step by step', 'guide me through', 'show me how', 'learn while doing', 'I want to understand', 'help me learn', 'can you explain how', 'what does this do and why', or when the user expresses desire to understand a topic deeply rather than just get a quick answer. Also trigger when the user wants to learn a new tool, library, pattern, or workflow hands-on — even if they don't use the word "teach". NOT for open-ended brainstorming (use /brainstorm), NOT for quick one-off explanations (just answer directly), NOT for debugging (use /dbg).
    12 repo stars
  53. ▌
    Tdd 3 · alexandrbasis bundle
    Test-driven development with red-green-refactor loop using vertical slices. Use when building features or fixing bugs with TDD, when /si or /si-quick needs canonical TDD discipline, when user mentions "red-green-refactor", "tracer bullets", "test-first", or asks for integration-style tests. Forbids horizontal slicing (all tests then all implementation).
    12 repo stars
  54. ▌
    Udoc 3 · alexandrbasis
    Update documentation for a completed implementation and, when the repository uses one or the user requests it, update its changelog. NOT for creating new product docs (use /product).
    12 repo stars
  55. ▌
    Quick 3 · alexandrbasis
    Apply a small change with known scope or a diagnosed bug fix using a compact task record. Use for quick fixes, configuration edits and bounded refactors; use /ct when the work needs unresolved design or coordinated implementation planning.
    12 repo stars
  56. ▌
    Setup 3 · alexandrbasis bundle
    Configure claudops for a specific repository after copying the workflow or installing the plugin. Use for first setup, requested reconfiguration, or unresolved project placeholders in claudops files.
    12 repo stars
  57. ▌
    Analyze 3 · alexandrbasis
    Compare a task's discovery or product requirements with its tech decomposition and report traceability gaps. Use when asked to 'analyze consistency', 'check alignment', 'verify spec matches plan', 'traceability check', 'spec drift', 'are my docs aligned', or after /ct completes to verify the plan covers the requirements. `/ct` may invoke this check when traceability is material; otherwise it remains an explicit read-only command. NOT for code review (use /sr), NOT for code analysis (use /code-analysis), NOT for debugging (use /dbg).
    12 repo stars
  58. ▌
    Product 3 · alexandrbasis
    Create a JTBD or PRD that records the user problem, evidence, scope, and measurable outcome through an interactive product interview. Use when asked to 'create JTBD', 'write a PRD', 'product requirements', 'jobs to be done', 'product documentation', 'product spec', or when a feature needs formal product-level documentation before technical planning. Conducts research, interviews, and pressure-tests the product thinking before writing. NOT for technical decomposition (use /ct), NOT for feature discovery (use /nf).
    12 repo stars
  59. ▌
    Finisher 3 · alexandrbasis
    Ship an existing implementation by committing local changes, pushing an open PR, waiting for green CI, and merging it. Use when the user explicitly asks to 'merge the PR', 'ship it', 'merge and close', 'commit push merge', 'finalize this PR', or 'land this branch'. Do not trigger on generic end-of-work language without a resolved PR or branch destination. This flow works with or without a task directory; phase handoff details live in Gate 3. NOT for opening a new PR (use plain `gh pr create`). NOT for addressing review comments (use /prc). NOT for preparing a session handoff to a fresh context (use /ph).
    12 repo stars
  60. ▌
    Grill Me 3 · alexandrbasis
    Use when a plan, design, or discovery document needs stress-testing for hidden assumptions, scope gaps, unresolved branches, or ambiguous wording; also when the user explicitly says "grill me".
    12 repo stars
  61. ▌
    Zoom Out 3 · alexandrbasis
    Step up one layer of abstraction and produce a map of the relevant modules and their callers — used when you (or the agent) are stuck in one file and losing the bigger picture. Use when user says "zoom out", "give me a map", "I'm lost in this code", or "what calls this".
    12 repo stars
  62. ▌
    Blueprint 3 · alexandrbasis
    Turn a one-line objective into a bounded staged implementation plan with cold-start briefs. Use when asked to 'blueprint', 'multi-session plan', 'long-term plan', 'construction plan', 'break into sessions', 'plan across sessions', 'multi-step project plan', 'session plan', or when work needs staged handoffs. Produces a plan where each step can be resumed independently by a fresh agent with no prior context.
    12 repo stars
  63. ▌
    Cc Linear 3 · alexandrbasis bundle
    Execute Linear operations via direct GraphQL API — create issues, update status/priority/title, add comments, search tasks, manage labels, assign work, and link PRs. Use this skill when the user mentions Linear explicitly, or references a Linear-style identifier (uppercase team prefix + dash + number, e.g. ENG-123, OPS-7; the project's team key is in $LINEAR_TEAM_KEY). Trigger on phrases like "create a Linear ticket/issue", "move TEAM-X to done/in progress/review", "update the Linear task status", "close the Linear issue", "what's in our Linear backlog", "assign this Linear issue to", "my Linear issues", or any project management operation targeting Linear. Also trigger when other skills (ct, si, sr) need to sync state with Linear. Do not trigger on ambiguous "create an issue" when the user clearly means a GitHub Issue (repo context, `gh issue` commands, issues.md), unless they also reference Linear.
    12 repo stars
  64. ▌
    Codex CLI 3 · alexandrbasis bundle
    Run OpenAI Codex CLI for one-shot cross-AI code review or approach validation. Invoke ONLY when the user explicitly asks ('second opinion', 'codex review', 'ask codex', 'run codex', 'cross-AI check'), or when another skill passes an explicit instruction to delegate to codex. Do not invoke proactively on general review requests. Not for interactive conversations.
    12 repo stars
  65. ▌
    Brainstorm 3 · alexandrbasis
    Compare options and clarify a decision through a collaborative brainstorming session. Use when asked to 'brainstorm', 'let's brainstorm', 'explore ideas', 'think through', 'brainstorm about [topic]', 'what are our options for', 'let's think about', 'pros and cons of', 'help me decide', or 'weigh the options'. NOT for feature discovery (use /nf), NOT for PRD/JTBD docs (use /product), NOT for deep research (use /deep-research), NOT for pre-implementation design (auto-triggered by design-exploration skill).
    12 repo stars
  66. ▌
    Cursor CLI 3 · alexandrbasis bundle
    Run Cursor CLI for one-shot cross-AI code review when a Cursor perspective is explicitly wanted. Invoke ONLY when the user asks ('cursor review', 'ask cursor', 'run cursor'), or another skill explicitly delegates to Cursor. Do not invoke it implicitly for a generic review. Not for interactive conversations.
    12 repo stars
  67. ▌
    Dev Server 3 · alexandrbasis
    Start any project's dev server and monitor it for errors in real-time. Universal — works with Node.js (Next.js, Vite, Remix, Astro, SvelteKit, Nuxt, Angular, Gatsby, Expo), Python (Django, Flask, FastAPI, Uvicorn), Ruby (Rails, Sinatra), Go, Rust (Cargo), Java (Spring Boot, Gradle, Maven), PHP (Laravel, Symfony), Elixir (Phoenix), and Docker Compose. Auto-detects the stack and package manager from project files. Uses the Monitor tool to stream only errors, warnings, and crashes — not routine request logs. Use this skill whenever the user says "start dev server", "run dev", "start the app", "launch the server", "npm run dev", "cargo run", "python manage.py runserver", "rails server", "go run", or anything that implies starting a local development server. Also trigger when the user asks to "monitor the server", "watch the build", "check for errors while I work", or simply "dev".
    12 repo stars
  68. ▌
    Triage Issue 3 · alexandrbasis
    Investigate a reported bug, find its root cause, and file a tracker issue (GitHub or Linear) with a TDD-based fix plan. Mostly hands-off — minimize questions to the user. Does NOT apply the fix. Use when user reports a bug and wants it tracked, mentions "triage", "file an issue", or "investigate and plan a fix". NOT for interactive debugging (use /dbg) or batch QA sessions (use /qa).
    12 repo stars
  69. ▌
    Update Setup 3 · alexandrbasis bundle
    Inspect or apply upstream claudops changes to a project's copied .claude/ workflow. Use for claudops update checks, selected upstream adoption, or conflicts with local workflow customizations. Installed plugin upgrades use the host's plugin manager.
    12 repo stars
  70. ▌
    Code Analysis 3 · alexandrbasis bundle
    Analyze the structure and quality of the current codebase with evidence-backed metrics, patterns, and recommendations. Use for an explicit code audit, architecture assessment, codebase overview, hotspot/complexity question, module-dependency analysis, or pre-implementation exploration. Do not use for pre-merge review (use /sr), runtime debugging (use /dbg), or external-technology research (use /deep-research).
    12 repo stars
  71. ▌
    Deep Research 3 · alexandrbasis
    Research an external, current, niche, or unfamiliar technical topic with cited evidence. Use for explicit research, comparisons, technology evaluation, migration/dependency decisions, or questions whose answer depends on sources outside the local codebase. Do not use for quick brainstorming (use /brainstorm), feature discovery (use /nf), or static local code analysis (use /code-analysis).
    12 repo stars
  72. ▌
    Git Guardrails 3 · alexandrbasis
    Inspect, install, customize, or troubleshoot the harness-level git safety hook that blocks dangerous git operations (push, branch -D, checkout .) before they execute. Use when the user wants to change which git commands are blocked, verify the guard is wired up, or set it up after a fresh clone.
    12 repo stars
  73. ▌
    Antigravity CLI 3 · alexandrbasis bundle
    Run Google Antigravity CLI (agy) for web-grounded research, cross-AI review, or validation when those capabilities are explicitly needed or another skill delegates to agy. One-shot only; do not select it for an ordinary review without an explicit provider choice.
    12 repo stars
  74. ▌
    Parallelization 3 · alexandrbasis
    Parallelize genuinely independent implementation items when /si or the user asks for parallel work. Use /si directly for one item, dependent work, shared files, or shared mutable state.
    12 repo stars
  75. ▌
    Coding Conventions 3 · alexandrbasis
    Internal reference skill — coding standards and patterns for developer agents. Not user-invocable.
    12 repo stars
  76. ▌
    Design Exploration 3 · alexandrbasis bundle
    Explore codebase and design approaches before implementation. Use when asked 'explore the design', 'how would this fit', 'design exploration', 'what patterns exist for', 'how is X implemented', or when another skill (brainstorm, nf) needs codebase context to ground a design proposal. NOT for code review (use /sr), NOT for static analysis (use /code-analysis).
    12 repo stars
  77. ▌
    Review Conventions 3 · alexandrbasis
    Internal reference skill — shared conventions for all code review agents. Not user-invocable.
    12 repo stars
  78. ▌
    Ubiquitous Language 3 · alexandrbasis
    Build or update a DDD-style ubiquitous language glossary when the user explicitly asks to define domain terms, build/update the project glossary, or harden terminology. For /nf, /product, or /ct context-reading calls, load and report the glossary; for authorized post-grill updates, merge and write it. Do not write for a load-only or explanatory request. NOT for architectural vocabulary (use /architecture-language).
    12 repo stars
  79. ▌
    Architecture Language 3 · alexandrbasis bundle
    Canonical architectural vocabulary — module, interface, seam, adapter, depth, leverage, locality. Use when reviewing architecture, deepening shallow modules, designing interfaces, or evaluating refactor candidates. NOT a domain glossary (use /ubiquitous-language for that).
    12 repo stars
  80. ▌
    Improve Codebase Architecture 3 · alexandrbasis bundle
    Explore a codebase for architectural deepening opportunities: refactors that turn shallow modules into deeper ones with better testability and locality. Use when the user explicitly asks for architecture improvement, refactoring opportunities, or coupled-module analysis. Do not use for pre-merge review (use /sr) or spec gaps (use /ct). Read-only; it does not write code.
    12 repo stars
  81. ▌
    Ct 2 · alexandrbasis bundle
    Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.
    12 repo stars
  82. ▌
    Nf 2 · alexandrbasis bundle
    Runs an in-depth feature-discovery interview that explores, challenges, and documents a new feature before planning. Use when asked to 'detail a feature', 'explore a new feature', 'feature discovery', 'interview about feature', 'spec out a feature', 'design a feature', 'think through a feature', 'deep dive on a feature', 'discover [feature-name]', or 'what should we consider for [feature]'. NOT for quick brainstorming (/brainstorm), PRD/JTBD docs (/product), or implementation tasks (/ct).
    12 repo stars
  83. ▌
    Ph 2 · alexandrbasis
    Prepare session handoff for continuation in a new conversation. Use when 'prepare handoff', 'save progress', 'session handoff', 'I need to stop', 'prepare for next session', 'hand off', 'write handoff', or when the user wants to pause mid-implementation and resume later in a fresh context window.
    12 repo stars
  84. ▌
    QA 2 · alexandrbasis
    Interactive QA session where the user reports bugs conversationally and the agent files them as tracker issues (GitHub or Linear) one by one or as a dependency-linked breakdown. Explores the codebase in the background for context and domain language. Use when user wants to "do QA", "report bugs", "file issues from a QA pass", or runs through multiple problems at once. NOT for single-bug triage (use /triage-issue) or interactive debug (/dbg).
    12 repo stars
  85. ▌
    Si 2 · alexandrbasis bundle
    Implement or resume a task from its existing plan and acceptance criteria, with behavior-first tests and recorded verification. Use for requested implementation; unresolved discovery belongs to /nf, planning to /ct, and independent review to /sr.
    12 repo stars
  86. ▌
    Sr 2 · alexandrbasis bundle
    Use when asked to review code before merge or review a PR, branch, commit range, task path, or current working tree. Trigger on requests like 'review PR', 'review my changes', 'review this branch', 'is this ready to merge', or other pre-merge review requests. Supports task/spec-aware review when task docs exist. NOT for addressing review comments (use /prc).
    12 repo stars
  87. ▌
    Vp 2 · alexandrbasis bundle
    Create interactive visual prototype playground for user approval before technical decomposition. Use when asked to 'create prototype', 'visual mockup', 'preview design', 'design playground', 'show me the feature', 'what would this look like', 'mockup the UI', 'visualize the architecture', 'preview before building', 'let me see the design', or anytime the user wants to see or approve a visual representation of a feature before coding begins. Also trigger when /nf discovery is complete and the user says 'looks good, let's see it', 'now show me', or 'visualize this'. NOT for brainstorming (use /brainstorm), NOT for feature discovery (use /nf), NOT for implementation tasks (use /ct), NOT for quick one-off diagrams (use /generate-web-diagram).
    12 repo stars
  88. ▌
    Dbg 2 · alexandrbasis
    Debug mode with runtime evidence and instrumentation. Use when asked to 'debug this', 'find the bug', 'troubleshoot', 'why is this broken', 'investigate runtime issue', 'it's not working', 'getting an error', 'this crashes', 'unexpected behavior', or when the user pastes an error message or stack trace and wants to find the root cause. Also trigger when the user describes behavior that differs from expectations in a running app. NOT for static code analysis without reproduction (use /code-analysis). NOT for CI pipeline failures (use /fci).
    12 repo stars
  89. ▌
    Fci 2 · alexandrbasis
    Fix CI pipeline failures blocking PR merge. Use when CI checks fail, 'pipeline broken', 'build failing', 'fix CI', or 'checks not passing'. NOT for debugging runtime bugs (use /dbg), NOT for code review (use /sr).
    12 repo stars
  90. ▌
    Prc 2 · alexandrbasis
    Review and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR comments', or 'address CR comments'. NOT for initiating code review (use /sr), NOT for task-based implementation with CR mode (use /si).
    12 repo stars
  91. ▌
    Rip 2 · alexandrbasis
    Review a technical implementation plan for business-value alignment and scope fit. Use when asked to 'review my plan', 'walk through implementation', 'check plan against PRD', 'review technical decomposition', or 'is my plan aligned with requirements'. NOT for code review (use /sr), NOT for creating tasks (use /ct), NOT for static code analysis (use /code-analysis).
    12 repo stars
  92. ▌
    Sbs 2 · alexandrbasis
    Interactive teaching guide for learning while working. Use when asked to 'teach me', 'walk me through', 'explain step by step', 'guide me through', 'show me how', 'learn while doing', 'I want to understand', 'help me learn', 'can you explain how', 'what does this do and why', or when the user expresses desire to understand a topic deeply rather than just get a quick answer. Also trigger when the user wants to learn a new tool, library, pattern, or workflow hands-on — even if they don't use the word "teach". NOT for open-ended brainstorming (use /brainstorm), NOT for quick one-off explanations (just answer directly), NOT for debugging (use /dbg).
    12 repo stars
  93. ▌
    Tdd 2 · alexandrbasis bundle
    Test-driven development with red-green-refactor loop using vertical slices. Use when building features or fixing bugs with TDD, when /si or /si-quick needs canonical TDD discipline, when user mentions "red-green-refactor", "tracer bullets", "test-first", or asks for integration-style tests. Forbids horizontal slicing (all tests then all implementation).
    12 repo stars
  94. ▌
    Setup 2 · alexandrbasis bundle
    Configure claudops for a specific repository after copying the workflow or installing the plugin. Use for first setup, requested reconfiguration, or unresolved project placeholders in claudops files.
    12 repo stars
  95. ▌
    Analyze 2 · alexandrbasis
    Compare a task's discovery or product requirements with its tech decomposition and report traceability gaps. Use when asked to 'analyze consistency', 'check alignment', 'verify spec matches plan', 'traceability check', 'spec drift', 'are my docs aligned', or after /ct completes to verify the plan covers the requirements. `/ct` may invoke this check when traceability is material; otherwise it remains an explicit read-only command. NOT for code review (use /sr), NOT for code analysis (use /code-analysis), NOT for debugging (use /dbg).
    12 repo stars
  96. ▌
    Product 2 · alexandrbasis
    Create a JTBD or PRD that records the user problem, evidence, scope, and measurable outcome through an interactive product interview. Use when asked to 'create JTBD', 'write a PRD', 'product requirements', 'jobs to be done', 'product documentation', 'product spec', or when a feature needs formal product-level documentation before technical planning. Conducts research, interviews, and pressure-tests the product thinking before writing. NOT for technical decomposition (use /ct), NOT for feature discovery (use /nf).
    12 repo stars
  97. ▌
    Finisher 2 · alexandrbasis
    Ship an existing implementation by committing local changes, pushing an open PR, waiting for green CI, and merging it. Use when the user explicitly asks to 'merge the PR', 'ship it', 'merge and close', 'commit push merge', 'finalize this PR', or 'land this branch'. Do not trigger on generic end-of-work language without a resolved PR or branch destination. This flow works with or without a task directory; phase handoff details live in Gate 3. NOT for opening a new PR (use plain `gh pr create`). NOT for addressing review comments (use /prc). NOT for preparing a session handoff to a fresh context (use /ph).
    12 repo stars
  98. ▌
    Grill Me 2 · alexandrbasis
    Use when a plan, design, or discovery document needs stress-testing for hidden assumptions, scope gaps, unresolved branches, or ambiguous wording; also when the user explicitly says "grill me".
    12 repo stars
  99. ▌
    Quick 2 · alexandrbasis
    Apply a small change with known scope or a diagnosed bug fix using a compact task record. Use for quick fixes, configuration edits and bounded refactors; use /ct when the work needs unresolved design or coordinated implementation planning.
    12 repo stars
  100. ▌
    Zoom Out 2 · alexandrbasis
    Step up one layer of abstraction and produce a map of the relevant modules and their callers — used when you (or the agent) are stuck in one file and losing the bigger picture. Use when user says "zoom out", "give me a map", "I'm lost in this code", or "what calls this".
    12 repo stars