agentleFS
Sign inStart free
ucdavisucdavis/ai-skills-registry/.github/skills/git-workflow-release/SKILL.md

git-workflow-release

Skill9 starsChanged 8 months agoMITView on GitHub

Standardized process for committing changes and releasing a new version. Includes steps for bumping versions in package files, updating the CHANGELOG.md, ensuring the README.md is up to date, and creating git release tags. Use when the user asks to "prepare a release", "bump the version", or "release a new version".

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. swap-cameroon/kuro-antigravity-config★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these instructions to safely and consistently release a new version of the project.

    line 8
  2. Distinctive:

    Ensure there are no untracked files or uncommitted changes (unless they are part of the release).

    line 11
  3. Very specific:

    Ensure all tests pass (npm test or the language equivalent).

    line 12
  4. Distinctive:

    README.md: Ensure the README.md reflects any new features, installation steps, or usage examples introduced since the last release.

    line 15
  5. Very specific:

    Add a new section at the top of the changelog for the new version (e.g., ## [1.2.0] - YYYY-MM-DD).

    line 17
  6. Very specific:

    Update the version number in all necessary files.

    line 27
  7. Very specific:

    Commit with a standard release message subject, and explicitly list the summarized release changes (e.g.

    line 31
  8. Distinctive:

    Create an annotated git tag for the new version.

    line 37
  9. Distinctive:

    Hotfixes: If releasing a critical bug fix, bump the PATCH version and ensure the changelog explicitly calls out the fix.

    line 51
  10. Very specific:

    Pre-releases: Use -alpha, -beta, or -rc suffixes (e.g., 1.2.0-beta.1) if preparing a pre-release version for testing.

    line 52

≈ “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

Git Workflow: Release Process

Follow these instructions to safely and consistently release a new version of the project.

1. Verify Clean Workspace and Tests

  • Ensure there are no untracked files or uncommitted changes (unless they are part of the release).
  • Ensure all tests pass (npm test or the language equivalent).

2. Update Documentation

  • README.md: Ensure the README.md reflects any new features, installation steps, or usage examples introduced since the last release.
  • CHANGELOG.md:
    • Add a new section at the top of the changelog for the new version (e.g., ## [1.2.0] - YYYY-MM-DD).
    • Categorize changes into Added, Changed, Deprecated, Removed, Fixed, or Security.
    • Review recent commit messages (git log) to capture all user-facing changes.

3. Bump the Version Number

  • Consult the current version using package.json (or the language equivalent, such as pyproject.toml or Cargo.toml).
  • Determine the new version number using Semantic Versioning (SemVer):
    • MAJOR version for incompatible API changes.
    • MINOR version for adding functionality in a backward-compatible manner.
    • PATCH version for backward-compatible bug fixes.
  • Update the version number in all necessary files. For Node.js projects, use npm version <major|minor|patch> --no-git-tag-version if appropriate, or edit package.json manually.

4. Commit the Release Changes

  • Stage the package.json, CHANGELOG.md, README.md, and any other updated metadata files.
  • Commit with a standard release message subject, and explicitly list the summarized release changes (e.g. from the CHANGELOG.md) in the commit body using a multi-line format or multiple -m flags:
    git commit -m "chore(release): bump version to v<NEW_VERSION>" -m "Changed: Updated dependencies and added SemVer guidelines."

5. Tag the Release

  • Create an annotated git tag for the new version.
    git tag -a v<NEW_VERSION> -m "Release v<NEW_VERSION>"

6. Push Changes

  • Push the release commit and the new tag to the remote repository.
    git push origin main
git push origin v<NEW_VERSION>
  • Note: Replace main with the appropriate default branch if different.

Edge Cases

  • Hotfixes: If releasing a critical bug fix, bump the PATCH version and ensure the changelog explicitly calls out the fix.
  • Pre-releases: Use -alpha, -beta, or -rc suffixes (e.g., 1.2.0-beta.1) if preparing a pre-release version for testing.

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