القائمة
Analyze changes since last release and bump crate versions
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Talk to a caldir provider binary directly via its JSON protocol to debug sync issues. Use when investigating "Provider error" messages, suspected wrong/missing event data from a provider, or when you need to see exactly what a provider returns before it goes through caldir-core. Triggers: "what does the provider return for X", "why is X showing up in status", "is this a parsing bug or a Google/iCloud/Outlook bug", investigating any provider-emitted error.
Read, create, edit, and sync calendar events as plaintext .ics files using the caldir CLI. Use whenever the user wants to query, add, modify, or sync calendar events — e.g. "what's on my calendar this week", "add a meeting tomorrow at 3", "cancel my Friday standup", "sync my Google calendar". Requires the `caldir` CLI.
| name | bump |
| description | Analyze changes since last release and bump crate versions |
| user_invocable | true |
Analyze git history since the last release and recommend semver bumps for each crate, then apply them.
There are 7 crates to consider:
| Crate | Cargo.toml path |
|---|---|
caldir-core | caldir-core/Cargo.toml |
caldir-cli | caldir-cli/Cargo.toml |
caldir-provider-google | caldir-provider-google/Cargo.toml |
caldir-provider-icloud | caldir-provider-icloud/Cargo.toml |
caldir-provider-caldav | caldir-provider-caldav/Cargo.toml |
caldir-provider-outlook | caldir-provider-outlook/Cargo.toml |
caldir-provider-webcal | caldir-provider-webcal/Cargo.toml |
caldir-cli and all caldir-provider-* crates depend on caldir-core — their caldir-core dependency version pin must always match core's version.
Find the latest v* git tag:
git tag -l "v*" --sort=-v:refname | head -1
Show the user which anchor you're using and how many commits are since it. If no tag exists, or the tag looks stale/wrong, ask the user which commit to use as the anchor.
git log <anchor>..HEAD --oneline
If there are no commits since the anchor, inform the user there's nothing to bump and stop.
For each commit, check which crate directories were modified:
git diff --name-only <anchor>..HEAD
Map changed files to crates by directory prefix (caldir-core/, caldir-cli/, caldir-provider-google/, caldir-provider-icloud/, caldir-provider-caldav/, caldir-provider-outlook/, caldir-provider-webcal/). Ignore changes outside these directories (root Cargo.toml, .agents/, etc.).
All crates are pre-1.0, so use these conventions:
If a crate had no changes but caldir-core was bumped, it still needs its caldir-core dependency pin updated — but its own version only bumps (patch) if the core changes affect it. Use your judgment.
Show a table like:
Crate Current → Proposed Reason
caldir-core 0.3.0 → 0.4.0 New sync field added (minor)
caldir-cli 0.3.0 → 0.4.0 New command + core bump (minor)
caldir-provider-google 0.2.1 → 0.2.2 Bug fix (patch)
caldir-provider-icloud 0.1.2 → (no change) Core dep pin updated only
Ask the user to confirm or adjust before applying.
Edit all relevant Cargo.toml files:
version fieldcaldir-core dependency pins in cli/provider crates to match core's new versionThen run cargo check to validate and update Cargo.lock.
Do NOT create a git commit or git tag — a GitHub Action automatically creates the tag on push.