Create a version-bump/release skill

[krisrowe]

Problem

Every time a version bump comes up across any repo, the process
is ad-hoc. The agent doesn't know whether to bump major/minor/patch,
where the version lives, whether to tag, whether to push tags,
or how to coordinate version across pyproject.toml and other files.
This causes churn every time.

Proposed solution

Create a version-bump/release skill that handles:

• Reading current version from pyproject.toml (the single source
  of truth)
• Bumping major, minor, or patch based on user input or
  conventional commit analysis
• Creating a git tag (e.g., v0.2.0)
• Pushing the commit and tag
• Optionally creating a GitHub release

The skill should work for any Python project with a
pyproject.toml. It should not introduce a second source of truth
(no __version__ in __init__.py — pyproject.toml is enough).

Scope

• Python projects using pyproject.toml for version
• Git tags following vX.Y.Z convention
• Optional GitHub release creation via gh CLI
• Should be invocable as /release or /version-bump

Work breakdown

• Design skill — what inputs, what outputs, what checks
• Implement skill
• Register in echoskill or claude-coding plugin
• Test on mcp-app and echofit repos