agentleFS
tradingstrategy-aitradingstrategy-ai/web3-ethereum-defi/.claude/skills/make-release/SKILL.md

make-release

Skill830 starsChanged 10 days agoMITView on GitHub

Prepare a new release by updating version, changelog, and building the package

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create a commit with the message Preparing a release.

    line 42
  2. Very specific:

    Verify the build succeeds and the output .tar.gz and .whl filenames contain the correct version number.

    line 52
  3. Distinctive:

    After a successful build, tell the user:

    line 56

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Make release

This skill prepares a new release of the web3-ethereum-defi package.

Required inputs

  1. Version number - The version string for the new release (e.g., 1.1, 2.0)

Steps

1. Update version in pyproject.toml

Edit the version field in pyproject.toml to the new version number.

2. Update CHANGELOG.md

  1. Find the # Current heading in CHANGELOG.md
  2. Rename it to # {version} (the new version number)
  3. Append today's date in parentheses to every changelog entry in that section that is missing a date
  4. Insert a new # Current section at the very top of the file with a single placeholder entry:
# Current

- TODO

# {version}

...existing entries...

3. Create a git commit

Finish with clean-up-for-pr at the outermost task's review handoff.

Create a commit with the message Preparing a release. Push to the master.

4. Build the package

Run:

poetry build

Verify the build succeeds and the output .tar.gz and .whl filenames contain the correct version number.

5. Prompt the user

After a successful build, tell the user:

Release {version} built successfully. Please upload to PyPI manually.

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.