Skills, plugins and agents for Software development

Use for Node.js debugging that needs inspector access: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths.

Python Debugpy

Use when Python code needs interactive debugging: hidden locals, confusing state mutation, failing tests, subprocesses, long-running services, or remote/headless attach.

tmux

Use for existing interactive tmux sessions. For one-shot commands, use normal shell. For new non-interactive background jobs, use background execution.

governance agent

You are the governance sub-agent for technical documentation.

Control UI E2E

Use this for Control UI changes that need a real browser flow with deterministic Gateway data.

Testing & quality

Diagram Maker

Create diagrams as artifacts, not prose. Choose one output mode:

Tag Duplicate PRs and Issues

Use this skill when a maintainer needs to decide whether a pull request or issue is a duplicate of existing work.

gh issues

Use for issue-to-PR automation. Prefer `gh` CLI; fall back to `gh api` only when a high-level command lacks the needed field.

Gitcrawl

Use local GitHub issue/PR archives before live GitHub search. Check freshness first:

GitHub

Use `gh` for GitHub. Use `git` for local commits/branches/push/pull. Use code-reading tools for deep reviews.

oracle

Oracle bundles a prompt + selected files for one second-model pass. Treat output as advisory; verify against code + tests.

inventory agent

You are the inventory sub-agent for technical documentation.

docs framework agent

You are the docs-framework sub-agent for technical documentation.

Using Git Worktrees

Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available.

Systematic Debugging

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Test Driven Development (TDD)

Write the test first. Watch it fail. Write minimal code to pass.

Testing & quality

Finishing a Development Branch

Guide completion of development work by presenting clear options and handling chosen workflow.

Code Review Reception

Code review requires technical evaluation, not emotional performance.

Verification Before Completion

Claiming that work is complete without verification is dishonest, not efficient.

Testing & quality

Writing Plans

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code