| engineering | capture-rule | auto | Qualifies an insight as reusable and non-obvious, routes it to exactly one home (target repo .claude/rules, harness .claude/rules-ex, harness .claude/rules, or auto-memory), dedups against existing rules on the same topic, and writes a focused kebab-case rule file with the correct paths: frontmatter for that home. | 📄 |
| engineering | commit-changes | auto | Assesses the working tree with git status/diff, stages everything if nothing is staged, drafts a Conventional Commits message matched to the diff, and commits. | — |
| engineering | create-adr | auto | Finds the target repo's existing ADR convention (or creates docs/adr/ starting at 0001), gathers the decision, context, alternatives, and consequences from the conversation, drafts a numbered ADR, and writes it after user approval. | 📄 |
| engineering | create-feature-branch | auto | Confirms the target repository and the feature/branch name, verifies it is actually in that repo (git rev-parse --show-toplevel), updates the local main branch from the remote, then creates and switches to a feature/<slug> branch (following the repo's own prefix convention if different). | — |
| engineering | create-manual-test-guide | auto | Determines the change under test (named feature/branch/PR or the current diff), reads the changed files to derive real test scenarios (happy path, edge cases, error handling, regression checks) and real launch/setup commands, then generates one self-contained interactive HTML guide with a test-flow SVG diagram, per-scenario pass/fail/skip toggles persisted to localStorage, and a Copy-results-as-Markdown export button. | 📄 |
| engineering | create-onboarding-guide | auto | Explores the repository (layout, architecture traced from real imports, 2-3 key flows traced end-to-end with file:line hops, conventions and gotchas) and generates one self-contained HTML onboarding tour with an SVG architecture diagram, collapsible directory map, flow walkthroughs, a recommended reading order, and real getting-started commands. | 📄 |
| engineering | create-pull-request | auto | Resolves the target repository from the active project context, runs bundled scripts (analyze_changes.mjs, generate_pr_body.mjs from a template matched to branch intent, quality_checks.mjs) in the target repo, then presents a localized PR title/body draft for approval before creating or updating the GitHub PR with gh. | 📄 |
| engineering | create-review-guide | auto | Determines the review scope (named range, dirty tree, or feature branch vs merge-base), reads every changed file in full and traces callers, then generates one self-contained HTML review guide with an overview, an SVG architecture diagram highlighting changed modules, a file/responsibility map, a collapsible annotated change walkthrough in recommended reading order, and a reviewer checklist. | 📄 |
| engineering | develop-small-feature | explicit | Carries a small, well-scoped change through the full lifecycle by chaining other components: create-feature-branch (if on the default branch), the tdd skill delegated to the implementer agent, static checks via the test-runner agent, an explicit stop for manual user verification of the uncommitted work, then commit-changes and create-pull-request. | — |
| engineering | install-recommended-skills | explicit | Checks gh auth, then runs gh skill install for six mattpocock/skills engineering skills (improve-codebase-architecture, tdd, to-issues, to-prd, codebase-design, grill-with-docs), continuing past individual failures and reporting a summary. | — |
| engineering | investigate-bug-report | auto | Diagnoses a reported bug without changing code: pins the report down to one given-X-does-Y-should-do-Z statement, reproduces the failure (or statically traces the code path when reproduction is infeasible), isolates the root cause to a specific file:line with git blame corroboration, classifies every caller for blast radius, and proposes 1-3 fix candidates plus the regression test that would have caught it. | — |
| engineering | prepare-release | auto | Creates a release/v<VERSION> branch from the up-to-date default branch, bumps the version in every version-bearing file (regenerating lockfiles), shows the commit history since the last tag and curates CHANGELOG.md with the user (Keep a Changelog format), then commits (chore(release): prepare v<VERSION>) and opens a PR to the default branch with the changelog as the body. | 📄 |
| engineering | set-openspec-path | explicit | Reads .claude/project-context.json, presents the registered projects as an AskUserQuestion menu (plus a Clear option), and rewrites only the openspecPath value to <chosen project>/openspec, preserving every other field. | 📄 |
| engineering | setup-all | explicit | Runs all four engineering setup phases in sequence, continuing past failures: installs the recommended mattpocock/skills set via gh, installs the OpenSpec CLI globally and runs openspec init --tools claude, scaffolds .claude/project-context.json if missing, and scaffolds the rules-ex files from the setup-rules-ex templates. | 📄 |
| engineering | setup-openspec | explicit | Verifies Node.js >= 20.19.0, installs @fission-ai/openspec globally if absent, runs openspec init --tools claude in the current project, and reports the newly available /opsx:* commands. | 📄 |
| engineering | setup-project-context | explicit | Shows the existing .claude/project-context.json if present (and stops), otherwise creates it from a template with roleBasedDelegation, openspecPath, postToolFormatCommands, and projects placeholders, then explains how each field drives the plugin's SessionStart/PreToolUse/PostToolUse hooks and that changes take effect at the next session start. | 📄 |
| engineering | setup-rules-ex | explicit | Scaffolds the two files the inject-extended-rules hook needs, copying the canonical templates from the skill's assets/templates/ and never overwriting existing files: a path-scoped authoring-guide rule and the rules-ex README. | 📄 |
| obsidian | defuddle | auto | Fetches a web page with the Defuddle CLI (defuddle parse <url> --md) instead of WebFetch, stripping navigation, ads, and clutter to return clean Markdown (or specific metadata via -p), saving tokens. | — |
| obsidian | json-canvas | auto | Creates and edits .canvas files per the JSON Canvas 1.0 spec: generates unique 16-hex-char node/edge IDs, positions nodes without overlap, connects them with validated fromNode/toNode edges, and re-validates JSON and reference integrity after every change. | 📄 |
| obsidian | kb-index | auto | Updates PARA Knowledge Base indexes using a 3-tier strategy: by default a smart diff that compares each _index.md against the files actually on disk and processes only additions/removals; --full rebuilds every index from the template; --category limits scope; --dry-run previews. | 📄 |
| obsidian | kb-ingest | auto | Processes new documents (from Inbox/ or a given path) into the PARA vault: reads and classifies each document to a PARA category using index files for context, plans a subdirectory-first destination and canonical filename before moving, generates frontmatter, creates wikilinks and backlinks, and updates the affected indexes and activity log. | 📄 |
| obsidian | kb-init | auto | Sets up the Knowledge Base layer on an existing PARA-structured vault: detects the vault root via .obsidian/, generates an _index.md in each PARA category from the template, creates the top-level index and append-only activity log, appends KB rules to AGENTS.md, and detects whether the obsidian CLI is available. | 📄 |
| obsidian | kb-lint | auto | Audits the vault's health read-only (or auto-fixes safe issues with --fix): index drift against files on disk, orphan documents with no links/index entries/tags, tag consistency (#proj/ and #type/ conventions), and broken wikilinks — via the obsidian CLI when available, Grep otherwise. | — |
| obsidian | kb-query | auto | Answers questions about vault content by picking the fastest search route (direct folder access, tag cross-collection, backlink traversal, or index+log browse) rather than always starting from the top-level index, synthesizes an answer across documents with wikilink citations, and can optionally save the insight back as a vault note. | — |
| obsidian | obsidian-bases | auto | Creates and edits Obsidian .base files (YAML database views over notes): defines filters, computed formula properties, property display config, summaries, and one or more table/cards/list/map views, then validates YAML syntax, quoting rules, and formula references. | 📄 |
| obsidian | obsidian-cli | auto | Reference for driving a running Obsidian instance through the obsidian CLI: parameter/flag syntax, file targeting by wikilink-style name or exact path, vault targeting, and common commands for reading/creating/appending notes, search, daily notes, properties, tasks, tags, and backlinks — plus plugin/theme development commands. | — |
| obsidian | obsidian-markdown | auto | Syntax reference for authoring valid Obsidian Flavored Markdown: wikilinks (heading/block variants), embeds (![[...]] for notes, images, PDFs), callouts, frontmatter properties, and when to prefer wikilinks over standard Markdown links — with deeper references in bundled PROPERTIES/EMBEDS/CALLOUTS files. | — |
| obsidian | zenn-blog-writing | auto | Japanese-language guideline skill for writing, editing, and reviewing Zenn tech-blog articles: the draft-to-publish workflow (published: false, npm run textlint, preview, publish), required frontmatter and topics naming rules, and prose-quality rules that emphasize technical accuracy and avoiding AI-sounding phrasing. | — |
| obsidian | zenn-markdown | auto | Syntax reference for Zenn-specific Markdown: message blocks, accordions (:::details), code-block filename/diff extensions, embedded content (link cards, videos, SNS), KaTeX math, mermaid diagrams, and image size/caption controls. | — |
| productivity | create-claude-command | auto | Reference guide for authoring Claude Code slash commands in a project's .claude/commands/: the scaffold template, $ARGUMENTS/$1 handling, @file and !command injection, naming conventions, and when to use a command vs agent vs skill. | 📄 |
| productivity | create-claude-md | auto | Inspects the project (build/test/lint config, README, git log conventions) and writes a concise CLAUDE.md that includes only what Claude cannot infer (commands, non-default style rules, workflow conventions, gotchas), routing domain-specific rules to .claude/rules/<domain>.md stubs and keeping the file under ~50 lines where possible. | 📄 |
| productivity | create-readme | auto | Investigates the project first (audience/README type, identity, run commands, features, assets, git remote), then writes a README ordered around the dominant intent (consumption, library, or contribution focused) using a prioritized section menu, GFM formatting, verified badges, and GitHub admonitions — never inventing commands or badges it cannot verify. | 📄 |
| productivity | create-release-notes | auto | Collects commits between the last tag and HEAD (or a given range), enriches thin commits from merged PRs via gh, filters out internal-only changes, and writes user-facing notes ordered by impact (Breaking/New/Improved/Fixed) with each item stating the user benefit rather than the implementation. | 📄 |
| productivity | create-work-log | auto | Scans the repositories configured in the skill's config.json for git activity in the period (commits on all branches by the configured author, plus uncommitted work), groups it by repo and Conventional Commit theme, asks the user for anything git can't show (or notes auto-generated when unattended), and saves a Markdown log. | 📄 |
| productivity | generate-html-report | auto | Picks one of five report modes (spec/plan, code-review explainer, design prototype, research/status report, or throwaway editing UI), gathers the real content first (source, git, MCPs, web), and writes one self-contained HTML file with inline CSS/JS/SVG — used in place of any Markdown document that would cross ~100 lines or needs diagrams/interactivity. | 📄 |
| productivity | handoff-go | explicit | Writes a handoff document summarizing the current conversation (with a suggested-skills section, secrets redacted) to the OS temp directory, then runs the bundled dispatch.mjs which launches a fresh claude session that reads it — splitting a multiplexer pane (herdr/zellij), opening a new terminal window, or printing a paste-ready command as fallbacks. | 📄 |
| productivity | herdr | auto | Teaches control of the herdr multiplexer from inside it (requires HERDR_ENV=1): listing workspaces/tabs/panes, reading other panes' output, splitting panes and running commands in them, waiting on output or another agent's status, and sending text/keys — all via herdr CLI commands over a local unix socket. | — |
| productivity | install-recommended-skills | explicit | Checks gh auth, then installs three mattpocock/skills productivity skills (grill-me, handoff, writing-great-skills) at user scope via gh skill install, continuing past individual failures and reporting a summary. | — |
| productivity | install-skill | explicit | Parses a GitHub skills-repo tree URL (or an OWNER/REPO + path reference) into a repo and skill path, then installs it with gh skill install <repo> <skill-path> --agent claude-code and reports the result. | — |
| productivity | launch-team | explicit | Acts as conductor for a multi-agent team: settles 2-4 roles (one orchestrator), writes a self-contained brief and a team config JSON to the OS temp dir, then runs the bundled launcher.mjs which opens one named multiplexer pane per agent (herdr or zellij), writes the shared roster, and delivers the brief to the orchestrator. | — |
| productivity | manage-desktop-routines | explicit | Three branches for Claude Code Desktop local routines: create (collects taskId/description/self-contained prompt/schedule, calls create_scheduled_task, hands the user a post-creation checklist for folder/model/permissions), backup (dumps all tasks with prompts to a JSON file), and restore (recreates tasks missing on this machine from the backup, never overwriting existing ones). | 📄 |
| productivity | post-to-slack | explicit | Resolves a channel name to its Slack ID via slack_search_channels (and a mention name to <@USERID> via slack_search_users), then posts with slack_send_message (supporting thread replies) and returns the permalink. | — |
| productivity | setup-herdr | explicit | Checks for herdr in both Windows and WSL (PATH, known install dirs, running process), installs it via the official install scripts only after user confirmation, installs the Claude Code/OpenCode integrations, and edits shell profiles (PowerShell, bash, zsh) to auto-launch herdr — removing any zellij autostart block first. | — |
| productivity | setup-zellij | explicit | Checks for zellij in PowerShell and WSL, installs it (winget / apt / cargo) after user confirmation, then edits the four shell profiles to auto-launch zellij on startup, removing any herdr autostart block installed by setup-herdr first. | — |
| productivity | sidekick-go | auto | Spawns a persistent helper agent in an adjacent multiplexer pane (herdr or zellij): writes a self-contained brief to the OS temp dir, runs the bundled dispatch.mjs to open the sidekick's pane and wire two-way messaging over the shared bus, then iterates with it across rounds (replies arrive in the caller's own prompt) until a closing message ends the exchange. | — |
| productivity | wsl-vscode-doctor | explicit | Diagnoses why code . | 📄 |
| scrum | audit-epic-consistency | auto | Cross-checks an Epic's backlog against its code: refreshes the snapshot and repo sync if stale, uses .pm/repo/branch-diff.json to scope the investigation to files the Epic actually touched, audits every in-scope item for drift, gaps (missing acceptance.md), and clarity with file:line evidence from the dedicated read-only clone, then applies only user-approved fixes (acceptance.md edits directly, monday edits via monday-api-mcp). | 📄 |
| scrum | investigate-spike | auto | Identifies the spike item on the monday board, loads its question from the item plus saved updates and acceptance.md, syncs the Epic's dedicated repo clone (sync-repo.mjs), investigates read-only with file:line evidence until there is enough to decide, then writes a findings report and offers to post the conclusion back to the monday item. | 📄 |
| scrum | load-epic-context | auto | Primes a session with an Epic's state at minimal token cost: refreshes the backlog snapshot (save-all.mjs) and repo sync (sync-repo.mjs) when older than 60 minutes, then reads only the aggregates (summary.md, progress-history.json, repo-state.json, branch-diff.json, tail of commits.jsonl) — never individual item files — and briefs the user before offering to (re)write the summary. | 📄 |
| scrum | manage-drive-docs | auto | Finds, reads, edits, and reorganizes development docs in Google Drive by working directly on the locally synced Google Drive for desktop folder with standard file tools scoped to the configured driveDocsRootPath, falling back to the bundled drive-fs.mjs script for rename/move/delete/list operations and for non-ASCII WSL paths the standard tools cannot reach. | — |
| scrum | manage-monday-backlog | auto | Reads and updates the monday.com backlog primarily through the plugin's dependency-free CLI scripts (list-items, get-item, update-item-status, save-item/doc/updates/all, init-task, set-link, check-stale-links) which need only MONDAY_TOKEN and Node 18+, resolving the board id and Epic folders from .claude/scrum-context.json; the monday-api-mcp server is the optional path for operations beyond the scripts' surface. | 📄 |
| scrum | prepare-sprint-review | auto | Refreshes the Epic snapshot with save-all.mjs, classifies items in the sprint window (done / progressed / carried over), gathers demo material per Done item from its pbi folder's acceptance.md and evidence/ (marking items with no recorded evidence), and generates a self-contained HTML review document with metrics, a demo agenda with time-boxes, per-item cards, and discussion prompts. | 📄 |
| scrum | refine-backlog | auto | Audits every non-Done item (or a narrowed scope) against four readiness checks — acceptance criteria present, estimate present, size within threshold, outcome-stating title — proposes concrete fixes (drafted Given/When/Then criteria, concrete splits, rewritten titles; never invented estimates), and applies only user-approved changes: criteria to the item's acceptance.md, board edits via the monday-api-mcp server or a paste-ready list. | — |
| scrum | report-epic-spec | explicit | Reconciles what the product does today vs what is planned by reading both sides: board items by status from .pm/backlog/ plus prd/prd.md, and the code via branch-diff.json, recent commits, and targeted reads in the dedicated clone — flagging Done items with no implementation trace and implemented behavior no item records — then writes a stakeholder-readable HTML report. | 📄 |
| scrum | report-pbl-progress | explicit | Runs the bundled generate-progress-report.mjs once against the Epic's Drive snapshot, which computes totals, status mix, and a completion forecast (assumed velocity until 2+ days of history exist, then measured) and renders the HTML report itself; the skill then resolves the report's Drive link and sharing status via the Drive MCP connector and reports the KPIs — never re-deriving aggregates from item files. | 📄 |
| scrum | setup-scrum-context | auto | Creates or updates the project's .claude/scrum-context.json without hand-editing: shows current values, extracts the board id from a pasted monday URL, sanity-checks that new mondayEpics folders fall under driveDocsRootPath, then pipes a JSON patch to the bundled init-scrum-context.mjs which merges onto the existing config and ensures the file is git-ignored. | 📄 |
| scrum | snapshot-pbl-to-drive | explicit | One-shot wrapper that runs save-all.mjs once for the named Epic (board id and Drive folder auto-resolve from scrum-context) and reports the script's JSON summary — deliberately never opening individual snapshot files afterward. | 📄 |
| scrum | write-retrospective | auto | Facilitates then records a KPT retrospective: prepares sprint facts from the board (done/carry-over, plus a follow-up verdict on every previous Try action), walks the user through Keep/Problem/Try one pass at a time with data-grounded candidate observations, turns Try items into owned, dated actions, saves the record, and offers to put actions on the monday board via monday-api-mcp. | 📄 |
| stack-cloudflare | cloudflare-static-assets | auto | Guides configuring Cloudflare Static Assets for React Router apps on Workers — adding the assets binding to wrangler.jsonc and creating a utility module that fetches public/ files uniformly across dev (Vite fetch), production (ASSETS binding), and build time (filesystem) — fixing the dev-works/prod-404 mismatch. | — |
| stack-dnd-kit | dnd-kit-implementation | auto | Provides the implementation pattern for combining useSortable and useDroppable on the same container in dnd-kit (Kanban-style UIs): detect what is being dragged via useDndContext and conditionally switch refs/listeners so containers act as drop targets when items drag and as sortables when containers drag. | — |
| stack-opencode | opencode-log-investigation | auto | Diagnoses OpenCode runtime failures by opening the newest log under ~/.local/share/opencode/log/ (or the Windows equivalent) and searching for ERROR lines, with targeted workflows for plugin-loading issues (service=plugin), MCP server failures (service=mcp), session/tool errors, and the gotcha that plugin stdout/stderr never reaches the log file. | — |
| stack-react-router | react-router-v7-app | auto | Prescribes React Router v7 conventions: file-based routing in app/routes/ (folder routes, route groups, dot-notation nesting, excluding test files from route discovery), loader/action data patterns with typed Route.* props, arrow-function route components, ErrorBoundary usage, and meta/headers exports. | — |