agentleFS
mihai-dinculescumihai-dinculescu/tapo/.claude/skills/release-libs/SKILL.md

release-libs

Skill877 starsChanged 5 days agoMITView on GitHub

Release a new version of the tapo (Rust) and tapo-py (Python) crates together, sharing the same version number

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Determine the new version: Read the current version from tapo/Cargo.toml.

    line 12
  2. Very specific:

    Bump the versions: Update the version field in both:

    line 14
  3. Very specific:

    If a ## [MCP Unreleased][Unreleased] section exists elsewhere in the file, move it (with its body intact) so it sits immediately after the …

    line 22
  4. Very specific:

    Add a link reference [vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/vX.X.X to the link definitions at the bottom of the file …

    line 23
  5. Very specific:

    Commit: Run /commit with message chore(tapo): release vX.X.X.

    line 25
  6. Distinctive:

    Tag: Create an annotated git tag:

    line 27
  7. Distinctive:

    Push: Ask the user for confirmation, then:

    line 33
  8. Very specific:

    Create GitHub release: Ask the user for confirmation.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Release tapo & tapo-py

Release a new version of the tapo (Rust) and tapo-py (Python) crates. Both libraries are released simultaneously and share the same version number.

Steps

  1. Determine the new version. Read the current version from tapo/Cargo.toml. Ask the user what the new version should be if not provided.
  2. Bump the versions. Update the version field in both:
    • tapo/Cargo.toml
    • tapo-py/pyproject.toml
  3. Update changelog. In CHANGELOG.md:
    • Replace the heading ## [Python Unreleased][Unreleased] with ## [Python vX.X.X][vX.X.X] - YYYY-MM-DD (use the current date).
    • Replace the heading ## [Rust Unreleased][Unreleased] with ## [Rust vX.X.X][vX.X.X] - YYYY-MM-DD (use the current date).
    • Insert new empty ## [Rust Unreleased][Unreleased] and ## [Python Unreleased][Unreleased] sections (in that order) immediately above the newly versioned Rust section.
    • If a ## [MCP Unreleased][Unreleased] section exists elsewhere in the file, move it (with its body intact) so it sits immediately after the new ## [Python Unreleased][Unreleased] section, keeping all three Unreleased sections grouped at the top in the order Rust → Python → MCP.
    • Add a link reference [vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/vX.X.X to the link definitions at the bottom of the file (right after the [Unreleased] link).
  4. Commit. Run /commit with message chore(tapo): release vX.X.X.
  5. Tag. Create an annotated git tag:

    git tag -a vX.X.X -m "vX.X.X"
  6. Push. Ask the user for confirmation, then:

    git push && git push origin vX.X.X
  7. Create GitHub release. Ask the user for confirmation. Use the content under the ## [Rust vX.X.X][vX.X.X] and ## [Python vX.X.X][vX.X.X] headings from CHANGELOG.md as the release body, followed by a full changelog comparison link. The previous version (vP.P.P) is the tag before this release:

    gh release create vX.X.X --title "Tapo vX.X.X" --notes "$(cat <<'EOF'
    ## Rust
    
    <rust changelog content here>
    
    ## Python
    
    <python changelog content here>
    
    **Full Changelog**: https://github.com/mihai-dinculescu/tapo/compare/vP.P.P...vX.X.X
    EOF
    )"

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.