all publishers

drn

@drn source repo

94 published skills

  1. ▌
    Write Skill · drn
    Create or improve a Claude Code skill/slash command with best practices for structure, dynamic context, and safety. Use for creating new skills, improving existing ones, or learning skill authoring.
    23 repo stars
  2. ▌
    Rereview Loop · drn
    Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.
    23 repo stars
  3. ▌
    Plan · drn
    Generate an implementation plan from a PRD, tech spike, or feature spec and save it to context/plans/. Use for planning work, breaking down a PRD, or creating an implementation plan from a spec.
    23 repo stars
  4. ▌
    Ship · drn
    Full ship pipeline: /review + fix + /improve + fix + /merge in one command. Use when ready to ship a branch end-to-end.
    23 repo stars
  5. ▌
    Dream · drn bundle
    Scheduled KB maintenance — ingest meetings and Claude Code/Codex JSONL sessions, synthesize raw notes into existing topical docs (decisions, people changes, conventions), resolve conflicts, age out stale entries, fix frontmatter and links. Translates raw data into knowledge. Runs unattended; never asks for confirmation. Use for KB maintenance, knowledge base cleanup, dream consolidation, memory hygiene, or as a scheduled daily KB pass.
    23 repo stars
  6. ▌
    Equip · drn
    Analyze a spec, PRD, or codebase to identify missing skills and agents, propose them, then write them. Use for skill gap analysis, agent gap analysis, bootstrapping agent capabilities from a spec, or equipping a project with skills.
    23 repo stars
  7. ▌
    Merge · drn bundle
    Merge current branch to the default branch via GitHub PR merge. Use when ready to merge a PR or land a branch.
    23 repo stars
  8. ▌
    Wrapup · drn
    End-of-session checklist that detects loose ends — uncommitted changes, unmerged branches, learnings to capture, handoffs needed — and routes to the right skills. Use for session closeout, wrapping up, end of day, or "anything else to capture".
    23 repo stars
  9. ▌
    Improve · drn bundle
    Improve skills, capture context & knowledge. Use for skill iteration, capturing learnings, or upgrading agent context.
    23 repo stars
  10. ▌
    Rereview · drn
    Re-review with fresh eyes. Zero regressions. Go slow and analyze everything. Use for a paranoid final review before merging.
    23 repo stars
  11. ▌
    Cross Agent · drn
    Set up cross-agent skill infrastructure so skills work across Claude Code, OpenAI Codex, and GitHub Copilot. Use for multi-agent compatibility, skill migration, cross-agent sync.
    23 repo stars
  12. ▌
    Orchestrate · drn
    Plan and execute a dependency-aware build using available native delegation and optional model tiering, with single-agent fallback. Use when orchestrating a build, dynamic workflow, model-tiered build, fable workflow, or tiered agents in any harness.
    23 repo stars
  13. ▌
    Pr · drn
    Open a PR, wait for CI to pass, fix failures, address review comments, and loop until fully green. Use when opening a PR, fixing CI, or addressing review feedback.
    23 repo stars
  14. ▌
    Dev · drn bundle
    Iterative development with testing and code review using available native agents or single-agent execution. Use for building features, implementing changes, or coding tasks that need testing and review in any agent harness.
    23 repo stars
  15. ▌
    Batch Pr Review · drn bundle
    Review a batch of pull requests together, describe every change in plain language, and build a private Claude artifact that eases human review, with a severity-tagged and verified findings list. Use when asked to review several PRs, a stack of PRs, PRs listed in a Slack thread or message, or to summarize a batch of PRs for a reviewer.
    23 repo stars
  16. ▌
    Plannotator Review 2 · drn bundle
    Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.
    23 repo stars
  17. ▌
    Plannotator Annotate 2 · drn bundle
    Open Plannotator's annotation UI for a markdown file, converted HTML file, URL, or folder and then respond to the returned annotations.
    23 repo stars
  18. ▌
    Plannotator Setup Goal 2 · drn bundle
    Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
    23 repo stars
  19. ▌
    Plannotator Visual Explainer 2 · drn bundle
    Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
    23 repo stars
  20. ▌
    Archive 2 · drn
    Archive the current Argus task so it moves to the Archive section of the task list. Use at the end of a session when the work is done.
    23 repo stars
  21. ▌
    Hera Review 2 · drn
    Default, user-overridable code review methodology — the review CONTRACT (what to analyze, how to tag findings) that a broad finder follows when spawned inside a hera-spawn-review panel, or that runs standalone via /hera-review for a single-pass review outside a panel. Encodes ralph-review's review contract (behavior / delta / plan / regression / security / test-coverage audits, the canonical finding tags) without ralph's loop control, auto-fix execution, or OpenSpec-drift resolution flow — those stay with hera-spawn-review (the panel synthesizer + fix loop) or with the invoking user when this runs standalone. Named in a diligence profile's [panel] as review_skill = "hera-review" (the shipped default); a project overrides it freely with its own review_skill or review_instruction — swapping it never requires touching hera-spawn-review.
    23 repo stars
  22. ▌
    Argus Complete 2 · drn
    Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status.
    23 repo stars
  23. ▌
    Argus Schedule 2 · drn
    Manage recurring or one-shot tasks in the local Argus daemon via its HTTP API. Use when the user wants to schedule a task locally in argus, create a cron-driven task, fire X every weekday/hour/morning, fire something once at a specific future time (one-shot via run_once_at), set up an agent that needs local filesystem access (logs in ~/.argus, local databases, dotfiles), list or update existing argus schedules, or run an argus schedule now. Distinct from /schedule, which creates remote cloud routines without local access.
    23 repo stars
  24. ▌
    Hera Spawn Review 2 · drn
    Orchestrate a vendor-diverse review panel over a diff: resolve the project's diligence-profile [panel] via mcp__argus__profile_resolve, spawn each broad finder and corrective lens as an in-session Claude sub-agent injected with its configured review instruction, synthesize every finder's output into the canonical finding schema with cross-vendor confidence voting, run fix-verification, then fix-and-re-review until clean. Use when the user wants a panel / multi- reviewer pass over a diff beyond a single reviewer loop — reachable from any argus project, not just OpenSpec ones. This chunk ships Fable+Opus in-session finders only: a foreign finder id (e.g. codex) is a reserved grammar slot the glue SKIPS with a loud note — the foreign-reviewer-capture primitive it needs is deferred (see D-SCOPE, openspec/changes/add-cross-vendor-review/design.md). NOT ralph-review (single reviewer, OpenSpec-only, no panel, no vendor diversity) — this is its hera-aware sibling; ralph stays untouched for solo use.
    23 repo stars
  25. ▌
    Resolve Archetype Model 2 · drn
    Resolve a diligence profile's per-archetype model (and, where the dispatch mechanism accepts it, effort) for Claude's NATIVE sub-agent dispatch (the Agent/Task tool, or Workflow's agent()) — as opposed to hera worker spawn, which already gets this via internal/agent.ResolveModel. Use when a coordinator or pipeline skill dispatches a sequence of in-context sub-agent stages that map to archetypes (e.g. a migration stage ~ code_slice, a review pass ~ review, a CI-fix loop ~ ci_loop) and wants each stage to run at the project's configured model/effort instead of silently inheriting the caller's own default. Generalizes the pattern hera-spawn-review already uses for the review archetype's [panel] block to the other twelve archetypes. NOT for hera worker spawn (already handled by hera_spawn_worker's archetype param) — this is for work that stays in-session with no worktree/branch/PR of its own.
    23 repo stars
  26. ▌
    Hera Review Test Adversary 2 · drn
    Corrective review lens: interrogates the tests touched or added by a diff for false confidence, instead of reviewing the diff broadly for correctness (that's hera-review's job). Trusting a green test run is a systematic blind spot broad finders share — codex's blind spot #2 specifically (see openspec/changes/add-cross-vendor-review/design.md D2) — so this lens exists to distrust green by default. Named in a diligence profile's [[panel.lens]] as skill = "hera-review-test-adversary", model = "opus" (never a foreign backend — a model that shares the blind spot can't correct for it in itself). Runs standalone via /hera-review-test-adversary too.
    23 repo stars
  27. ▌
    Plannotator Review · drn bundle
    Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.
    23 repo stars
  28. ▌
    Plannotator Annotate · drn bundle
    Open Plannotator's annotation UI for a markdown file, converted HTML file, URL, or folder and then respond to the returned annotations.
    23 repo stars
  29. ▌
    Plannotator Setup Goal · drn bundle
    Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
    23 repo stars
  30. ▌
    Plannotator Visual Explainer · drn bundle
    Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
    23 repo stars
  31. ▌
    Hera 2 · drn
    Inside an argus sandbox (cwd under ~/.argus/worktrees/ or ARGUS_TASK_ID set), coordinate multi-agent work via hera's mcp__argus__hera_* tools — bootstrap an orchestrator, claim or attach a worker/freelance role, spawn workers, and message roles over the idle-gated bus. Load this skill when you are (or are becoming) a coordinator, when you're spawned as a hera worker, or before delegating work that must run as its OWN argus session (separate worktree / long-running agent / own PR / own sandbox) — as opposed to in-process Claude sub-agents, which stay the right tool for ephemeral in-session fan-out. For staged or dependency-ordered multi-worker plans, this skill routes you to the companion `hera-plan` skill. NOT for non-argus sessions, where these MCP tools are not registered.
    23 repo stars
  32. ▌
    Hera Plan 2 · drn
    The hera plan-DAG: author staged, dependency-ordered multi-worker plans inside an argus sandbox and let the daemon gater materialize each node into a born-bound worker as its blockers finish. Load this (in addition to the base `hera` skill) when you are a coordinator and the work decomposes into multiple hera worker units that have DEPENDENCIES among them (one stage needs another's output, or a required ordering) — internal dependencies are the clean signal to plan a DAG rather than spawn workers ad hoc. Covers the authoring/mutation verbs, gating-on-`done`, automatic branch-stacking and its fan-in footgun, short-id node naming, sub-coordinator nodes, and the self-guard prompt patterns. NOT for non-argus sessions; NOT for in-session ephemeral work (use Claude's native sub-agents); NOT for independent workers with no ordering (just spawn them).
    23 repo stars
  33. ▌
    New Phase · drn
    Plan and execute a new feature phase for Anthesis using the proven pinned-contract parallel workflow pattern. Use when starting a new major feature or phase.
    23 repo stars
  34. ▌
    Verify Live · drn
    Run Anthesis windowed with a SceneTree harness script to verify a change live: drive gameplay via command bus, capture screenshots, check for script errors. Use when asked to verify a change works in the real game, take screenshots, or test gameplay end-to-end.
    23 repo stars
  35. ▌
    Hera · drn
    Inside an argus sandbox (cwd under ~/.argus/worktrees/ or ARGUS_TASK_ID set), coordinate multi-agent work via hera's mcp__argus__hera_* tools — bootstrap an orchestrator, claim or attach a worker/freelance role, spawn workers, and message roles over the idle-gated bus. Load this skill when you are (or are becoming) a coordinator, when you're spawned as a hera worker, or before delegating work that must run as its OWN argus session (separate worktree / long-running agent / own PR / own sandbox) — as opposed to in-process Claude sub-agents, which stay the right tool for ephemeral in-session fan-out. For staged or dependency-ordered multi-worker plans, this skill routes you to the companion `hera-plan` skill. NOT for non-argus sessions, where these MCP tools are not registered.
    23 repo stars
  36. ▌
    Archive · drn
    Archive the current Argus task so it moves to the Archive section of the task list. Use at the end of a session when the work is done.
    23 repo stars
  37. ▌
    Hera Plan · drn
    The hera plan-DAG: author staged, dependency-ordered multi-worker plans inside an argus sandbox and let the daemon gater materialize each node into a born-bound worker as its blockers finish. Load this (in addition to the base `hera` skill) when you are a coordinator and the work decomposes into multiple hera worker units that have DEPENDENCIES among them (one stage needs another's output, or a required ordering) — internal dependencies are the clean signal to plan a DAG rather than spawn workers ad hoc. Covers the authoring/mutation verbs, gating-on-`done`, automatic branch-stacking and its fan-in footgun, short-id node naming, sub-coordinator nodes, and the self-guard prompt patterns. NOT for non-argus sessions; NOT for in-session ephemeral work (use Claude's native sub-agents); NOT for independent workers with no ordering (just spawn them).
    23 repo stars
  38. ▌
    Hera Review · drn
    Default, user-overridable code review methodology — the review CONTRACT (what to analyze, how to tag findings) that a broad finder follows when spawned inside a hera-spawn-review panel, or that runs standalone via /hera-review for a single-pass review outside a panel. Encodes ralph-review's review contract (behavior / delta / plan / regression / security / test-coverage audits, the canonical finding tags) without ralph's loop control, auto-fix execution, or OpenSpec-drift resolution flow — those stay with hera-spawn-review (the panel synthesizer + fix loop) or with the invoking user when this runs standalone. Named in a diligence profile's [panel] as review_skill = "hera-review" (the shipped default); a project overrides it freely with its own review_skill or review_instruction — swapping it never requires touching hera-spawn-review.
    23 repo stars
  39. ▌
    Argus Complete · drn
    Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status.
    23 repo stars
  40. ▌
    Hera Spawn Review · drn
    Orchestrate a vendor-diverse review panel over a diff: resolve the project's diligence-profile [panel] via mcp__argus__profile_resolve, spawn each broad finder and corrective lens as an in-session Claude sub-agent injected with its configured review instruction, synthesize every finder's output into the canonical finding schema with cross-vendor confidence voting, run fix-verification, then fix-and-re-review until clean. Use when the user wants a panel / multi- reviewer pass over a diff beyond a single reviewer loop — reachable from any argus project, not just OpenSpec ones. This chunk ships Fable+Opus in-session finders only: a foreign finder id (e.g. codex) is a reserved grammar slot the glue SKIPS with a loud note — the foreign-reviewer-capture primitive it needs is deferred (see D-SCOPE, openspec/changes/add-cross-vendor-review/design.md). NOT ralph-review (single reviewer, OpenSpec-only, no panel, no vendor diversity) — this is its hera-aware sibling; ralph stays untouched for solo use.
    23 repo stars
  41. ▌
    Resolve Archetype Model · drn
    Resolve a diligence profile's per-archetype model (and, where the dispatch mechanism accepts it, effort) for Claude's NATIVE sub-agent dispatch (the Agent/Task tool, or Workflow's agent()) — as opposed to hera worker spawn, which already gets this via internal/agent.ResolveModel. Use when a coordinator or pipeline skill dispatches a sequence of in-context sub-agent stages that map to archetypes (e.g. a migration stage ~ code_slice, a review pass ~ review, a CI-fix loop ~ ci_loop) and wants each stage to run at the project's configured model/effort instead of silently inheriting the caller's own default. Generalizes the pattern hera-spawn-review already uses for the review archetype's [panel] block to the other twelve archetypes. NOT for hera worker spawn (already handled by hera_spawn_worker's archetype param) — this is for work that stays in-session with no worktree/branch/PR of its own.
    23 repo stars
  42. ▌
    Hera Review Test Adversary · drn
    Corrective review lens: interrogates the tests touched or added by a diff for false confidence, instead of reviewing the diff broadly for correctness (that's hera-review's job). Trusting a green test run is a systematic blind spot broad finders share — codex's blind spot #2 specifically (see openspec/changes/add-cross-vendor-review/design.md D2) — so this lens exists to distrust green by default. Named in a diligence profile's [[panel.lens]] as skill = "hera-review-test-adversary", model = "opus" (never a foreign backend — a model that shares the blind spot can't correct for it in itself). Runs standalone via /hera-review-test-adversary too.
    23 repo stars
  43. ▌
    Skill Usage · drn
    Show skill usage statistics, charts, and suggestions for pruning unused skills. Use when the user asks "skill usage", "which skills do I use", "unused skills", "skill stats", or "skill suggestions".
    23 repo stars
  44. ▌
    Deploy Audit · drn
    Audit every commit pending between a base branch and a deployed branch/tag for deploy risk (migrations, config/secret wiring completeness, feature-flag defaults, schema parity), then open the GitHub compare diff. Use when asked to audit pending commits, check deploy risk, review what is about to ship, or before opening a deploy PR or shipping to production.
    23 repo stars
  45. ▌
    Argus Schedule · drn
    Manage recurring or one-shot tasks in the local Argus daemon via its HTTP API. Use when the user wants to schedule a task locally in argus, create a cron-driven task, fire X every weekday/hour/morning, fire something once at a specific future time or "in N minutes" (one-shot via run_once_at), set up an agent that needs local filesystem access (logs in ~/.argus, local databases, dotfiles), list or update existing argus schedules, or run an argus schedule now. Distinct from /schedule, which creates remote cloud routines without local access.
    23 repo stars
  46. ▌
    Bash Tool Path · drn
    Safely add a directory to Claude Code's Bash tool PATH. Use when a binary runs in your terminal but is "command not found" inside Claude Code's Bash tool, when adding a directory to PATH for Claude Code, when configuring CLAUDE_ENV_FILE, or when settings.json env.PATH did not work. Explains why env.PATH replaces rather than appends PATH and is not variable-expanded, why ~/.zshrc PATH exports are dropped, and the supported SessionStart hook fix.
    23 repo stars
  47. ▌
    CI Investigate · drn
    Investigate flaky CI failures across multiple workflow runs to identify patterns, categorize root causes, and propose fixes. Use when asked to investigate CI failures, find flaky tests, diagnose test flakiness, or understand why CI is failing repeatedly.
    23 repo stars
  48. ▌
    Prompt Summary · drn
    Summarize the prompts used in the current conversation as a numbered list. Use when the user wants to see the prompt chain, review their prompts, or share the sequence of prompts that produced a result.
    23 repo stars
  49. ▌
    Deploy Validate · drn
    Validate a deploy after it lands — CI status, rollout health, error tracking, and monitoring/alerting — correlating every finding against the deploy's start time to separate genuine regressions from pre-existing noise. Use when asked to validate a deploy, check post-deploy health, confirm a production rollout is healthy, or after a deploy finishes.
    23 repo stars
  50. ▌
    Devils Advocate · drn
    Execute the /devils-advocate workflow shared across Codex, Claude Code, and Copilot in this repository. Use when you want to stress-test ideas, challenge assumptions, or play devil's advocate.
    23 repo stars
  51. ▌
    Address Comments · drn
    Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.
    23 repo stars
  52. ▌
    Markdown Preview · drn bundle
    Render a Markdown file to GitHub-flavored HTML and open a styled local preview (light + dark) in the browser. Use when the user wants to preview markdown, see how a README renders on GitHub, check that relative screenshots or images display correctly, or get a GitHub-like local preview without installing grip or glow.
    23 repo stars
  53. ▌
    Plannotator Last · drn bundle
    Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
    23 repo stars
  54. ▌
    Orchestrate Stack · drn
    Orchestrate a stack of dependent Argus tasks that produce a chain of stacked PRs. Use when the user has a multi-milestone plan that should land as N PRs where each branches off the previous. Decomposes the plan into sub-tasks, wires base_branch + depends_on, embeds the closing protocol in every sub-task prompt, and polls until the stack lands.
    23 repo stars
  55. ▌
    Notion Address Comments · drn
    Iterate on a Notion page against its open inline comments — read each unresolved thread, edit the page to address it, and reply with a short summary of the change. Use when the user asks to address the comments in a Notion doc, address feedback left as inline Notion comments, or is running an iterative doc-drafting session where Notion comments are the direction.
    23 repo stars
  56. ▌
    PDF · drn bundle
    Use when the user wants to export conversation content, or an existing HTML file such as a saved Claude Artifact, to a professionally styled PDF for sharing
    23 repo stars
  57. ▌
    Tts · drn
    Read text aloud using text-to-speech. Use when the user says "speak to me", "read to me", "read this aloud", "say this", "speak the summary", or asks to hear something spoken.
    23 repo stars
  58. ▌
    Deps · drn
    Audit outdated dependencies, check for vulnerabilities, and upgrade with test verification. Use for dependency audits, security checks, or upgrading packages.
    23 repo stars
  59. ▌
    Eli5 · drn
    Explain any topic in the simplest possible terms using analogies and everyday examples. Use when the user says "explain like I'm 5", "eli5", "explain simply", "dumb it down", or "explain in simple terms".
    23 repo stars
  60. ▌
    Logo · drn
    Generate SVG logo alternatives with side-by-side comparison. Use when creating logos, branding, or project icons.
    23 repo stars
  61. ▌
    Loop · drn
    Run a prompt on a recurring interval using a blocking sleep loop. Use for polling CI, babysitting deploys, monitoring logs, periodic checks, or scheduled task execution.
    23 repo stars
  62. ▌
    Perf · drn bundle
    Before/after performance benchmarking comparing current branch against base, with statistical analysis. Use for benchmarking, profiling, or measuring performance impact.
    23 repo stars
  63. ▌
    Test · drn
    Intelligent test runner that targets changed code and identifies coverage gaps. Use for running tests, finding coverage gaps, or testing changed code.
    23 repo stars
  64. ▌
    Amend · drn
    Amend the last git commit with a useful, descriptive message. Use when you want to rewrite a commit message, amend commit description, or improve the last commit message.
    23 repo stars
  65. ▌
    Debug · drn
    Multi-agent competing hypotheses debugging. Use when stuck on a bug, need root cause analysis, or want competing debug theories.
    23 repo stars
  66. ▌
    Email · drn
    Search and read Gmail messages. Use when looking up emails, reading email threads, or checking inbox labels.
    23 repo stars
  67. ▌
    Guard · drn
    Pre-commit safety check for secrets, security antipatterns, and test breakage. Use for pre-commit checks, secret scanning, or verifying test safety.
    23 repo stars
  68. ▌
    Learn · drn
    Alias for /improve — improve skills, capture context & knowledge. Use for skill iteration, capturing learnings, or upgrading agent context.
    23 repo stars
  69. ▌
    Prune · drn bundle
    Clean up merged and stale git branches, prune old local and remote branches safely. Use for cleaning up old branches or pruning stale remotes.
    23 repo stars
  70. ▌
    Retro · drn
    Run a structured retrospective or post-incident review with optional knowledge base capture. Use for running retrospectives, postmortems, or incident reviews.
    23 repo stars
  71. ▌
    Slack · drn
    Query Slack channels, search messages, and fetch user information. Use when reading Slack data, checking channel history, searching messages, or looking up users.
    23 repo stars
  72. ▌
    Spike · drn
    Time-boxed technical investigation with structured findings document, tech spike, research spike, proof of concept. Use for time-boxed research, technical spikes, or proof of concept work.
    23 repo stars
  73. ▌
    Swarm · drn
    Conductor-native multi-agent orchestration with real-time progress. Use for parallel agent swarm, multi-agent tasks, agent team, team coordination, parallel workers.
    23 repo stars
  74. ▌
    Bisect · drn
    Find which commit introduced a bug using git bisect with automatic test verification. Use when tracking down which commit introduced a bug.
    23 repo stars
  75. ▌
    Deploy · drn bundle
    Deploy latest master to production with a version tag. Use when releasing to production or tagging a deploy.
    23 repo stars
  76. ▌
    Notion · drn
    Read Notion pages and databases using MCP tools. Use when looking up Notion content, reading pages, or querying databases.
    23 repo stars
  77. ▌
    Polish · drn bundle
    Analyze codebase for code smells and refactor to drastically improve code quality. Expert in clean code, SOLID principles, Ruby patterns, service objects, and refactoring. Use for code quality audits, refactoring sessions, and cleaning up technical debt.
    23 repo stars
  78. ▌
    Rebase · drn
    Rebase current branch onto latest upstream default branch and force-push to update PR. Use when updating a branch, rebasing onto main, or resolving conflicts.
    23 repo stars
  79. ▌
    Review · drn
    Code review panel for current branch changes. Use for reviewing PR changes, code review, or getting feedback on branch changes.
    23 repo stars
  80. ▌
    Slides · drn bundle
    Build a self-contained, single-file HTML presentation deck from talking points or a source doc, using a terminal/TUI-styled template with keyboard, tap, and swipe navigation. Use when the user wants to create slides, build a presentation or deck, turn talking points or a doc into a talk, make an HTML slideshow, or produce a presentation as a shareable artifact (instead of Google Slides).
    23 repo stars
  81. ▌
    Squash · drn
    Squash all branch commits into one and update open PRs. Use when squashing commits, cleaning up history, or condensing branch commits before merge.
    23 repo stars
  82. ▌
    Contest · drn
    Competing implementations with judge evaluation. Use when comparing multiple approaches, picking the best solution, or running a bake-off.
    23 repo stars
  83. ▌
    Explore · drn
    Multi-agent parallel research with peer-challenged synthesis. Use for deep research, codebase exploration, or investigating how something works.
    23 repo stars
  84. ▌
    Handoff · drn
    Generate a handoff prompt to pass context to another agent thread. Use when switching repos, handing off work, or sharing context between agents.
    23 repo stars
  85. ▌
    Migrate · drn
    Multi-agent codebase migration with module ownership. Use for large refactors, API upgrades, framework migrations, or bulk code changes.
    23 repo stars
  86. ▌
    Release · drn
    Create a versioned release with changelog generation, git tag, and GitHub release. Use for creating releases, tagging versions, or publishing changelogs.
    23 repo stars
  87. ▌
    Standup · drn
    Generate a daily standup summary from recent git activity, commits, open PRs, and current work in progress. Use for daily standup prep or summarizing recent work.
    23 repo stars
  88. ▌
    Complete · drn
    Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status.
    23 repo stars
  89. ▌
    Scaffold · drn
    Bootstrap new components, files, or modules matching existing repo conventions and patterns. Use for creating new files, components, or modules that follow repo patterns.
    23 repo stars
  90. ▌
    Changelog · drn
    Generate an intelligent changelog from recent commits. Use for release notes, version history, or documenting what changed.
    23 repo stars
  91. ▌
    Knowledge · drn
    Initialize or update a project knowledge base for durable cross-session knowledge capture. Use for setting up or updating project knowledge bases.
    23 repo stars
  92. ▌
    Prioritize · drn
    RICE-scored backlog prioritization. Use for sprint planning, feature prioritization, or backlog grooming.
    23 repo stars
  93. ▌
    Screenshot · drn
    View recent screenshots from ~/Downloads. Use when the user mentions "last screenshot", "see screenshot", "recent screenshot", "show screenshot", "last N screenshots", or references viewing screenshots from Downloads. Automatically finds and displays the most recent screenshot images sorted by creation time.
    23 repo stars
  94. ▌
    Combine Prs · drn
    Compare two competing PRs implementing the same feature, identify strengths of each, and combine the best parts into a single branch. Use when comparing PRs, combining implementations, cherry-picking between PRs, or resolving competing approaches.
    23 repo stars