Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jgravelle/release
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community. Load before any version bump, PyPI upload, tag, GitHub release, MCP registry publish, or PR merge.
Passed 19 of 21 test cases with the skill, and 6 of 21 without it.
and 12 more in the full report
13 fixed6 passed either way2 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to bump the package version in uv.lock. Should I run 'uv lock --upgrade' or manually edit the file?
| Checked | Without skill | With skill |
|---|---|---|
| Advises manually editing only the package version line in uv.lock | Missed | Passed |
The instructions your model reads when the skill loads.
REVISED 2026-09-04 (docs/workflows/DESIGN.md section 5). The PUBLISH half of this file (steps 4-7 below: local build,
twine upload,git tag,gh release create,mcp-publisher) is SUPERSEDED byrelease.yml, dispatched perdocs/cicd/RUNBOOK.mdsection 1; the/releasecommand prepares the release PR and stops. Those steps stay here as the record of the retired path and for RUNBOOK section 1a's hand-finish while PyPI persists no publisher (C-15). The PR-workflow and CLA halves are current. This copy is TRACKED in this repo; the suite copy underC:\MCPs\.claudeserves jdoc and jdata.
⚠⚠ THIS FILE MIXES TWO AUDIENCES AND THE SPLIT IS LOAD-BEARING. Almost every
command below is run BY THE AGENT through the Bash tool (Git Bash), so bash
syntax is correct for them: PYTHONPATH=src python ..., GITHUB_TOKEN="" gh ...,
BR=$(...). Inline env-var prefixes and $(...) do NOT exist in cmd.exe or
PowerShell, which is what jjg is at when he types.
Step 7 is the ONE command a HUMAN types interactively, and on 2026-08-13 it
failed mid-release because it had silently inherited bash path syntax from its
neighbours (~\mcp-publisher.exe -> "The system cannot find the path
specified"). The dev platform is Windows. Any line added here that a human
will type must be given in cmd.exe AND PowerShell form, with no ~, no inline
VAR=x cmd prefix, and no $(...). Mark the shell explicitly.
⚠⚠ BEFORE ANY OF THIS: are you holding the release for something that is not ours? A signature, a contributor PR, a reply, a re-run, "so it can go out together" — if the thing being waited for needs someone else to act, ship now and let them ride the next one. Policy 2 is not broken by anyone overruling it; it is broken by a batching argument that never mentions it (2026-08-18: five merged green fixes held two days to avoid three cheap conflict resolutions). "Reduce our churn" is not a release criterion — conflict resolution and re-merges are our costs to absorb, and the moment avoiding them shapes when users get fixes, we are spending their latency for our convenience. See CLAUDE.md policy 2e.
# 1. Bump EVERY pin site, not just pyproject.toml. jcm now has FOUR:
test cases passed, vs 6 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.