skills

Use when changing what a running devloop harness serves — pointing it at a different directory or worktree, or making the live harness serve newer or different code (a newer commit, another branch, or in-progress edits) without a wasteful restart.

Use when verifying that a UI change works end to end by driving the running app in a real browser — confirming a fix, reproducing a reported UI symptom, or proving a wizard/form/flow behaves — with Playwright against the exact code under review.

Enforce a Roborev plus Kata development workflow for code changes. Use when Codex is asked to implement, fix, refactor, or review work tracked by Kata and Roborev, especially when branch discipline, non-blocking review jobs, validation gates, SemVer, changelog checks, and final delivery reporting matter.

Use when working on GitHub pull requests that need PR-ready validation, review-thread replies, reviewer mentions, linked external references, or merge readiness checks.

Create or review a standalone repository that publishes a set of Codex or Claude skills with shared validation, linking, eval, and agent metadata conventions.

Prepare small, reviewable local commits with explicit rationale, SemVer impact, task hygiene, branch cleanup expectations, and clear commit commentary. Use when asked to commit work, prepare a PR-ready change, decide version impact, write commit messages, or clean up merged feature branches.

Use when classifying the priority of a Jira issue or creating a Jira issue with the correct priority assigned.

Add or review GitHub Actions CI for programming-language and skills projects, including README badges linked to workflow runs.

Review or design software architecture so changes stay local, explicit, testable, and observable. Use when code structure, module boundaries, interfaces, abstractions, tests, or error handling need architectural judgment.

Distinguish README synopsis work from actual documentation updates. Use when README, docs, CLI help text, man pages, GNU info files, changelog prose, or project documentation are changed or reviewed.

Use when working with the devloop local automation tool, devloop.toml files, watched workflows, managed processes, event endpoints, browser reload hooks, readiness or liveness probes, or devloop environment interpolation.

Select the narrowest deterministic validation for a change by its blast radius. Use when choosing tests, checks, CI gates, or manual validation before claiming work is done.

Prepare and execute a versioned release through a feature branch, PR, green CI, protected main, merged release commit, version tag, and tag-triggered release workflows when present. Use when Codex is asked to prepare, validate, publish, tag, or execute a release.

Configure GitHub repository policy for protected main, PR merge methods, CI-required merges, and tag-triggered artifact releases.

Use when tracking work with Beads or bd: creating issues, claiming ready work, updating issue notes, managing dependencies, closing completed work, or reporting Beads task hygiene.

Use when deciding changelog entries, maintaining [Unreleased], removing reverted unreleased entries, or preparing release version and changelog sections.

Use for every coding or script execution task. Applies to code edits and code reviews as well as tests builds validation debugging shell commands automation and blocked execution reports. Ensures exceptions are surfaced instead of muted.

Use when creating or updating skills in this repository, adding skill evals, changing SKILL.md instructions, preparing skill validation, or committing skill work. Keeps skills concise concrete and validated.

Decompose oversized, tangled, or multi-purpose Codex skills into a concise SKILL.md plus focused references, scripts, and assets. Use when creating or refactoring skills that exceed practical context size, mix unrelated workflows, duplicate reference material, hide resource selection rules, or need progressive disclosure.

Use this skill when creating or reorganising project documentation, especially deciding what belongs in README.md versus docs/. It keeps README concise and moves durable detail into focused docs.

Use when tracking work with Kata: creating task inventories, backlog lists, follow-up work, searching or creating issues, assigning active work, recording comments and relationships, closing verified work, or reporting Kata task hygiene.

Edit Markdown files with Markdown-appropriate Unicode. Use when creating or changing `.md`, `.markdown`, or `.mdx` files where box-drawing trees, typographic punctuation, arrows, symbols, accents, or other Unicode characters improve clarity or preserve the intended text.

Use when creating editing reviewing or running shell scripts, Bash scripts, sh files, repository scripts, automation wrappers, validation scripts, install scripts, CI helper scripts, or command-line glue code. Requires strict shell mode.

Use this skill for browser UI, realtime visualisation, and local web application work. It keeps the app running, inspects rendered behaviour, checks realtime flows, and validates deterministically.