Skills

Design language and guidance, and review for the Internals Viewer app

Create a pull request with proper branch, description, and labels

Carry out a task from work/tasks/ — the implementer agent writes the change, the reviewer agent checks it, findings go back for fixing; the user gets the summary and commits.

MacroQuest coordinator from the MQ docs repo - delegates to a documentation researcher or code expert agent. Use when the user asks how an MQ command, TLO, datatype, or plugin works and the rgmercs code doesn't answer it, or invokes /mq. Don't use for routine rgmercs edits that follow existing code patterns.

Open a pull request from the current branch, this repository's way

Commit the current changes on a new branch, push, and open a GitHub PR following this repo's conventions.

Run the quality gate (tests, build, lint) then open a pull request. Use when the user says "create a PR" or "open a PR".

# Pull request A PR is squash merged or rebase merged, never with a merge commit. Squashed, the title becomes the commit subject on main and the release-notes line. Rebased, every commit lands as it

Push the current jj bookmark, open a draft GitHub PR, link it to ClickUp, and move the task to in review.

Create a pull request with automatic quality checks, a conventional commit, and the gh CLI. Use when the user wants to open a PR or push a branch for review. Takes a package argument (blit386, demos, website, kit, create-blit386, or root for repo-wide files) to pick the right preflight gate and commit scope conventions.

Run the read-only Accounts Payable control engine over posting document sets (30 controls in 6 families, PASS/REVIEW/FAIL verdicts, byte-identical no-write guarantee). Use to check posting integrity, payment release gates, approver routing and duty segregation, information reporting, or commitment hygiene.

Plan implementation for a sufficiently clear feature or scoped task, including after /nf or /product. Use for 'create task', 'plan implementation', or 'technical decomposition'. Save a concise, executable plan in the existing task; use /nf for unresolved feature discovery and /si for implementation.