Menú
Cut a new semver release — bumps package.json, previews changelog, commits, tags, pushes, and verifies npm publish.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Prepare a code branch and pull/merge request for human review through safe rebasing, repository-specific validation, multiple independent subagent review rounds, evidence-based fixes, conventional commits, pushing, PR creation, and CI babysitting. Use when asked to prepare, polish, or finalize a PR/MR; obtain several reviews; iterate until clean; or make a branch ready for human review.
Debug an `imprint teach` run — env vars, CLI flags, log files, tracing, and diagnostic commands. Helps diagnose slow, stuck, or failing teach runs.
Refresh checked-in examples from generated Imprint site tools and cut an Imprint patch release. Use when the user asks to commit new generated tools to examples, replace stale example tool snapshots, update example docs/tests after generated tool repairs, or publish a patch release after example/runtime fixes.
Audit and repair generated Google Flights Imprint tools. Use when validating Google Flights search, calendar, booking, airline/bag filters, one-way, round-trip, multi-city, or open-jaw behavior; when investigating `selection_token` or `selected_flights` producer-consumer contracts; or when live audit results are slow, bot-sensitive, under-tested, or incorrectly waived as infrastructure.
Investigate a site's auth-tool compile — ongoing or completed. Locate the real agent transcript (not just the hook log), read the live 2FA verification, inspect the emitted workflow.json, confirm the login actually completed, and diagnose "no auth tool compiled".
Create a conventional commit from staged changes — picks type, scope, and writes the message.
| name | release |
| version | 1.0.0 |
| description | Cut a new semver release — bumps package.json, previews changelog, commits, tags, pushes, and verifies npm publish. |
| triggers | ["release","cut a release","bump version","new release"] |
| allowed-tools | ["Bash","Read","Edit"] |
Cut a new release for Imprint. Follow these steps in order.
Run git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline to see commits since the last tag.
Decide the bump type:
feat!: or BREAKING CHANGE in body)feat:)fix:, refactor:, perf:, docs:, chore:, etc.)If unsure, ask the user.
Read package.json and extract the current version field.
Apply semver bump to the current version. For example: 0.1.0 + minor = 0.2.0.
Edit package.json to set the new version string. Do not change anything else.
Run bunx git-cliff --config cliff.toml --unreleased --strip header and show the output to the user. Ask if it looks correct.
Stage and commit:
git add package.json
git commit -m "chore(release): v<VERSION>"
Use the exact version string. No Co-Authored-By trailer for release commits.
git tag v<VERSION>
Ask the user for confirmation, then:
git push && git push --tags
This triggers the release.yml workflow, which creates the GitHub Release, publishes the npm package, and uploads binaries.
Watch the release workflow:
gh run list --workflow release.yml --limit 1
gh run watch <RUN_ID> --exit-status
Then verify npm:
npm view imprint-mcp version
If GitHub Actions cannot publish and local npm auth is available, publish manually from the tagged commit:
npm whoami
npm publish --access public
Tell the user: "Release v<VERSION> tagged and pushed. GitHub Actions created the release at https://github.com/ashaychangwani/imprint/releases, and npm shows imprint-mcp@<VERSION>."