bump-core-req
Updates the minimum core version requirement for a fleet plugin in all three canonical places: `required_core_version` and `requires["claude-code-hermit"]` in…
Manage developing story arcs tracked across briefs — add, resolve, and list active arcs in compiled/story-arcs-*.md. Arc Watch keywords drive the feed-brief arc-tagging enrichment. Invoke with /feed-hermit:story-arcs add|resolve|list.
$ npx -y skills add gtapps/claude-code-hermit --skill story-arcs --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/story-arcsContext preview
The summary Claude sees to decide when to auto-load this skill.
Manage developing story arcs tracked across briefs — add, resolve, and list active arcs in compiled/story-arcs-*.md. Arc Watch keywords drive the feed-brief arc-tagging enrichment. Invoke with /feed-hermit:story-arcs add|resolve|list.
name: story-arcs description: >- Manage developing story arcs tracked across briefs — add, resolve, and list active arcs in compiled/story-arcs-*.md. Arc Watch keywords drive the feed-brief arc-tagging enrichment. Invoke with /feed-hermit:story-arcs add|resolve|list.
Manage the developing-story-arcs file that feeds the `feed-brief` arc-tagging enrichment.
/story-arcs add "<name>" [--started <YYYY-MM-DD>] [--watch "<keywords>"] [--context "<text>"] /story-arcs resolve "<name>" [--reason "<resolution note>"] /story-arcs list
Glob `.claude-code-hermit/compiled/story-arcs-*.md`. Sort by filename date suffix descending (newest first). Read the most recent. If none exists, create `.claude-code-hermit/compiled/story-arcs-<today>.md` with the standard template (frontmatter + `## Active` + `## Recently Resolved` sections).
Parse: `name` (required), `--started` (default: today, prefixed with `~`), `--watch` (optional keyword list), `--context` (optional description).
1. Check `## Active` — if an arc with the same name already exists (case-insensitive), say so and stop. 2. Append a new arc block at the end of `## Active`:
**<name>** (started: ~<YYYY-MM-DD>) <context text, or "Newly surfaced — add context as it develops."> Watch: <watch keywords separated by semicolons, or "TBD">.
3. Write the file in-place. Reply: `Arc added: **<name>**. Update the Watch clause with /story-arcs if needed.`
Parse: `name` (required, case-insensitive substring match), `--reason` (optional).
1. Find the arc block in `## Active`. If not found, list close matches and stop. 2. Remove the full arc block (the `**Name** (started:...)` line + context line + Watch line). 3. Insert a one-line entry at the top of `## Recently Resolved`:
**<name>** — <reason, or "resolved">. <today's date>
4. Write the file in-place. Reply: `Arc resolved: **<name>**. It will no longer be matched in future briefs.`
1. Display all arcs under `## Active` as a compact table: Name, start date, Watch keywords. 2. Show the count of `## Recently Resolved` entries. 3. If `## Active` is empty, say "No active arcs."
--- title: Developing Story Arcs type: story-arcs created: <ISO 8601> tags: [brief, foundational] --- Ongoing stories to track across briefs. Updated when arc status changes. ## Active **Arc Name** (started: ~YYYY-MM-DD) Context description. Pattern being tracked. Watch: keyword1; keyword2; keyword3. ## Recently Resolved **Arc Name** — resolution note. YYYY-MM-DD
filename date suffix; a new file would drift from the one being actively referenced.
automatically (it only reads `## Active`).
If you know Claude Tag, the idea will feel familiar: hand Claude work through a channel, such as Discord, Telegram, or your custom integration, and get results back there.
Repo: gtapps/claude-code-hermit
Updates the minimum core version requirement for a fleet plugin in all three canonical places: `required_core_version` and `requires["claude-code-hermit"]` in…
Changelog and commit — lightweight motion for day-to-day plugin dev work in the monorepo. One commit per plugin scope; CHANGELOG and staging routed by detected…
Documentation-drift audit for the plugin monorepo. Audits either each scoped plugin's unreleased changelog claims or its latest shipped release from the…
Explain in plain language what a fix, feature, PR, or plan will actually change for downstream hermits and the operators chatting with them — a before/after…
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings…
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, which branches went stale, and GitHub…