agentleFS
Sign inStart free
AlperenEvciAlperenEvci/claude-code-development-harness/.claude/skills/harness-release-bump/SKILL.md

harness-release-bump

Skill1 starsChanged 2 months agoMITView on GitHub

Perform a coordinated version bump of the development-harness plugin across the manifest, changelog, and any version-bearing documentation, then run the full gate. Invoke explicitly when cutting a new plugin release.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not commit, tag, or push.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

harness-release-bump

  • A release touches several files that must not drift apart. Work through them in order and confirm each one.
    1. Confirm the working tree is clean and you are on a feature branch, not main.
    1. Read the current version from plugins/development-harness/.claude-plugin/plugin.json.
    1. Collect the changes since that version. Prefer git log over memory, and group them into Added / Changed / Fixed / Removed.
    1. Update version in plugins/development-harness/.claude-plugin/plugin.json.
    1. Add a new dated section at the top of CHANGELOG.md using the existing heading format (## <version> — <YYYY-MM-DD>).
    1. Grep for the old version string across the repository and update any remaining occurrence that genuinely refers to the plugin version. Do not rewrite historical changelog entries.
    1. Check the compatibility: line in each SKILL.md and update it only if the minimum Claude Code or Python requirement actually changed.
    1. Run the full gate and report the real result: python scripts/validate_repo.py (or bash scripts/validate-repo.sh). Local Windows gate is supported; confirm CI on ubuntu-latest for privileged symlink and POSIX permission assertions.
    1. Review docs/publishing.md for any manual publication step that still needs a human.
  • Do not commit, tag, or push. Report what changed and stop.

User-supplied context:

$ARGUMENTS

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free