This skill should be used when investigating a reported bug, diagnosing a failure, or performing root-cause analysis — especially before concluding "not a bug", tracing a symptom, or explaining unexpected behavior. Preloaded on investigation agents.
This skill should be used when the user says "bye", "wrap up", "tear down", "we're done", or otherwise ends the session. It shuts down spawned teammates and agents, removes their worktrees, and reconciles uncommitted or unpushed session work.
This skill should be used when the user asks to "check PR comments", "verify review comments are addressed", or otherwise confirm that PR feedback is resolved in code. It can optionally produce a triage-compatible report.
This skill should be used when the user says 'ci-dance', 'make the PR green', 'ship this and fix CI', 'push and handle reviews', or wants end-to-end PR pipeline automation.
This skill should be used when preparing to dispatch work to Codex Sol, deciding whether to route coding to Codex, dispatching directly via codex-companion.mjs rather than the codex:codex-rescue subagent, handling a Codex job that fails to write or commit, monitoring a running Codex job, or recovering a stale Codex…
This skill should be used when developing, modifying, reviewing, or testing code. It defines universal rules for TDD, self-review, quality timing, review format, and security. MANDATORY for every agent performing such work — load at task start and apply continuously.
This skill should be used when preparing to delegate any task to an agent — a single Agent() spawn or a whole wave — or when the user says "spawn an agent", "delegate this", "parallelize this", "split this work", or "use a subagent". It also applies when choosing a model tier, batching small tasks, or deciding…
This skill should be used when the user asks to "merge dependabot PRs", "process dependency bumps", "auto-merge bot PRs", or "handle the dependabot backlog". It audits each dependency, comments findings, merges when CI is green, and requests rebases for conflicts or CI failures.
This skill should be used when coordinating multiple agents — spawning subagents, isolating worktrees, managing teams, scaling work, recovering failures, or managing a programme. Coordinator agents that spawn, manage, or merge subagent work always load it.
This skill should be used when the user requests a code review, audit, or quality assessment covering quality, security, dependencies, and documentation. It uses parallel agents and produces a deduplicated, severity-ranked report.
This skill should be used when extracting learnings, saving lessons, or capturing reusable knowledge from a session. It is also appropriate before presenting a plan, after notable events such as bugs or corrected approaches, and as the final task when work is complete.
This skill should be used when the user asks to "merge the base branch", "update this feature branch from base", or resolve conflicts while merging base into a feature branch.
This skill should be used when the user asks to "commit and push", "create a PR", "ship this", "send changes upstream", "open a pull request", or "publish this branch". It commits, pushes, creates a PR, and automatically creates a feature branch when currently on a base branch.
This skill should be used when the user asks to "bump the version", "cut a release", or "create a GitHub release". It applies SemVer 2.0, updates the changelog, commits, pushes, creates the release, and auto-detects Rust, Python, JS/TS, Claude Code plugin, and other supported stacks. Arguments are major, minor, patch…
This skill should be used when the user asks to "review a dependency update", "audit this dependency bump", or assess the security of an upgraded or newly added dependency.
This skill should be used when the user asks to "review this PR", "audit this pull request", or assess a PR for code quality, security, and correctness.
This skill should be used when implementing, fixing, writing, reviewing, or discussing Rust code quality, API design, safety, or idioms. It applies the Microsoft Pragmatic Rust Guidelines and Rust API Guidelines checklists.
This skill should be used when writing or reviewing code that handles authentication, cryptography, user input, secrets, or API endpoints. It provides OWASP-based secure programming practices and should be consulted proactively during reviews and planning.