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.

Tasks

Ensure CI is passing on the main branch
Ensure version is bumped in pacwich's package.json
- bun install must be ran to ensure bun.lock and generated docs (README.md etc.) are updated (should be committed + pushed)
Run and approve the publish workflow
After successful publish, use bun install again and push to ensure updated bun.lock for CI
Create a release tag with change notes (pre-made URL present in publish workflow summary)
Deploy documentation website to production
Maybe: deploy blog post for noteworthy release
- User will generally note upfront if this is needed, so assume it is unnecessary (usually not for most releases)

Más de este repositorio

mismo repositorio

manual-qa

smorsic/pacwich

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.

2026-07-2160

review-assist

smorsic/pacwich

Use to assist a manual review of the codebase

2026-07-2060

agent-qa

smorsic/pacwich

Instructions for agentic validation of pacwich by interacting with real monorepos against documentation.

2026-07-1560

doc-updates

smorsic/pacwich

Use when user is ready to work on documentation updates after unreleased changes have been made. Use

2026-07-0960

code-quiz

smorsic/pacwich

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.

2026-06-2260

name	release
description	Use when user is ready to release a new version of pacwich. Use

Release

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.

Tasks

Ensure CI is passing on the main branch
Ensure version is bumped in pacwich's package.json
- bun install must be ran to ensure bun.lock and generated docs (README.md etc.) are updated (should be committed + pushed)
Run and approve the publish workflow
After successful publish, use bun install again and push to ensure updated bun.lock for CI
Create a release tag with change notes (pre-made URL present in publish workflow summary)
Deploy documentation website to production
Maybe: deploy blog post for noteworthy release
- User will generally note upfront if this is needed, so assume it is unnecessary (usually not for most releases)