Menu
Use when user is ready to release a new version of pacwich. Use
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Guide the user step-by-step through performing QA of pacwich themselves (CLI, API, config), handing them copy-pasteable commands/code and doc pointers as they drive. Inverse of agent-qa.
Use to assist a manual review of the codebase
Instructions for agentic validation of pacwich by interacting with real monorepos against documentation.
Use when user is ready to work on documentation updates after unreleased changes have been made. Use
Quiz the user on the purpose of code in their repo. Picks a random file (git-tracked by default) and asks the user to explain either the file's overall purpose or that of a randomly-chosen utility inside it. Configure include/exclude globs and the git-tracked toggle via this skill's `config.json`. Invoke when the user asks to be quizzed.
| name | release |
| description | Use when user is ready to release a new version of pacwich. Use |
This is a skill that is performed after changes have are ready to be released.
Keep track of the listed tasks below as a checklist for the user. At this point,
source code changes and documentation have been completed, the doc-updates
skill already providing similar tasks for documentation performed before this.
Many of these tasks are simply for the user to confirm completion, since there aren't necessarily repo changes to review.
The user may specify that some of these tasks were already completed before using the skill. Simply mark these tasks as already done.
main branchpackage.json
bun install must be ran to ensure bun.lock and generated docs (README.md etc.) are updated (should be committed + pushed)bun install again and push to ensure updated bun.lock for CI