omnifocus-mcp: Skill for Claude Code

Release Workflow

This skill orchestrates a complete release. Follow each phase in order. Stop and report if any phase fails.

Phase 1: Milestone Check

Before creating a release branch, verify the milestone is ready.

1. Determine the target milestone. Look at open milestones:

   gh api "repos/{owner}/{repo}/milestones?state=open&sort=due_on" --jq '.[] | "\(.number) \(.title) open:\(.open_issues) closed:\(.closed_issues)"'
   

2. If there are multiple open milestones, ask the user which one to release.

3. If the target milestone has open issues, stop and ask the user:

   • List the open issues: gh api "repos/{owner}/{repo}/milestones/{number}/issues?state=open" --jq ... (or use gh issue list --milestone)
   • Present options: a. Move open issues to the next milestone (specify or create it) b. Pause to work on the open issues first c. Close the issues if they're no longer relevant
   • Do NOT proceed until all issues in the target milestone are closed or moved.

4. Once the milestone is clean (0 open issues), proceed.

Phase 2: Version Number

1. Read the current version from pyproject.toml (authoritative source).
2. The milestone title tells you the target version (e.g., v0.7.3 means version 0.7.3).
3. Validate it's a valid semver bump from the current version.
4. Present the version to the user for confirmation: "Release version X.Y.Z? (current: A.B.C)"
5. Wait for confirmation before proceeding.

Phase 3: Create Release Branch

git checkout main
git pull origin main
git checkout -b release/vX.Y.Z

Phase 4: Bump Version

Update version in ALL of these files (pyproject.toml is authoritative):

1. pyproject.toml - version = "X.Y.Z"
2. src/omnifocus_mcp/init.py - __version__ = "X.Y.Z"
3. CLAUDE.md (.claude/CLAUDE.md) - **Version:** vX.Y.Z in the header line
4. README.md - All references to the old version (check with grep for old version string)

Use the Edit tool for each file. Be precise about what to change.