dev-setup

Fix breakage on a Dependabot PR. Trigger when (a) the current branch matches `dependabot/*` and CI is red, (b) the user asks to "fix the dependabot PR" / "make this dependency update pass", or (c) the user invokes `/dependabot-fix [pr-number]`. Reads failing CI logs and upstream CHANGELOG, applies a bounded fix loop, pushes commits to the Dependabot branch, comments residual risks on the PR. Never merges. Aborts honestly when the fix needs human judgment.

Cut a tagged GitHub release from the default branch. Trigger when the user says "ship a release", "cut a release", "tag a release", or invokes the skill explicitly. Auto-sizes the semver bump from conventional-commit prefixes in the commit range since the last tag — patch / minor / major — and respects an explicit size hint (`patch|minor|major`) or exact version (`vX.Y.Z`). Writes CHANGELOG.md, tags, pushes, creates the GitHub release. Aborts if the tree is dirty, the default branch isn't pushed, or the tag already exists.

Fix breakage on a Dependabot PR. Trigger when (a) the current branch matches `dependabot/*` and CI is red, (b) the user asks to "fix the dependabot PR" / "make this dependency update pass". Reads failing CI logs and upstream CHANGELOG, applies a bounded fix loop, pushes commits to the Dependabot branch, comments residual risks on the PR. Never merges. Aborts honestly when the fix needs human judgment.

Bug triage pipeline — Report → Analyze → Fix → Verify. Use instead of harness-plan+harness-work for bugs. Prefixed harness- for consistency with the other phase skills.

Turn a brief into .harness/PLAN.md with per-task verification criteria. No code written — implementation is the harness-work skill. Prefixed harness- to avoid collision with Codex's built-in /plan (which has different semantics).

Pre-merge gate — verify plan done, gates green, CI passing, docs swept. Does NOT push/merge/tag without explicit user approval. Prefixed harness- for consistency with the other phase skills.

Adversarial review — assume the code has bugs, find them. Executable artifact required. No fixes applied. Prefixed harness- to avoid collision with Codex's built-in /review (which has different semantics).

First-time project scaffold for agentm. Populates init.sh with real commands, verifies it boots, seeds AGENTS.md, features.json, and the wiki/ scaffold. Run once per project. Prefixed harness- to avoid collision with Codex built-ins. Does not plan — planning is the harness-plan skill.

Implement exactly one task from .harness/PLAN.md. Stop after one. Runs .harness/verify.sh after implementing (Codex's PostToolUse hook is Bash-only, so per-write verify is not available — gates run in-skill). Prefixed harness- for consistency with the other phase skills.

Cut a tagged GitHub release from the default branch. Trigger when the user says "ship a release", "cut a release", "tag a release". Auto-sizes the semver bump from conventional-commit prefixes in the commit range since the last tag — patch / minor / major — and respects an explicit size hint (`patch|minor|major`) or exact version (`vX.Y.Z`). Writes CHANGELOG.md, tags, pushes, creates the GitHub release. Aborts if the tree is dirty, the default branch isn't pushed, or the tag already exists.

Cross-model adversarial reviewer. Shells out to the Gemini CLI via .harness/scripts/cross-review.sh for a second opinion from a different model. Same contract as adversarial-reviewer — failing test, DEFECT file:line, or NO ISSUES FOUND. No prose. Gracefully falls back to the in-process adversarial-reviewer when gemini is unavailable. Dispatched first in the /review workflow to escape the same-model echo chamber.

Critic for recently-written code. Framing is literal — "the code contains bugs, find them." Required output is a failing test, a specific file:line defect, or an explicit no-issues finding with categories checked. Prose-only critiques are rejected. Dispatched in the /review workflow after deterministic gates pass. Fresh context; the implementer's reasoning trace is deliberately withheld.

Structural maintainer of the wiki/ documentation tree. Dispatched at phase boundaries only (setup, plan, work post-gates, release, bugfix). Creates, updates, and prunes pages to reflect what the codebase actually does. Preserves human edits. Never touches code. Write scope is restricted to wiki/** and .harness/project.json. Declines mid-/work invocations — runs only after gates are green.

Read-only codebase exploration skill. Dispatch when you need to answer a question about where code lives or how it works, and returning raw tool output would waste main-context. Returns a structured summary with file:line references — never writes or edits files. Use this skill whenever a single focused question about the codebase comes up mid-workflow.