Claude Cursor opencode Skill

bump-skill

Internal agentic-workflow maintenance: after SKILL.md edits, bump semver, lint authoring rules, and synchronize changelogs, READMEs, routing metadata, and migrations. Triggers: "bump the skill", "update the changelog", "version bump".

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download gtrabanco-agentic-workflow-skills_bump-skill-4b3a56b.zip · 4 KB
Part of gtrabanco/agentic-workflow — 33 skills

Install

skills CLI npx skills add https://github.com/gtrabanco/agentic-workflow/tree/main/skills/bump-skill
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install gtrabanco-agentic-workflow@llmmart
Git git clone https://github.com/gtrabanco/agentic-workflow.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole gtrabanco/agentic-workflow collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Turn contract — verify before ending the turn

✓ Every changed skill's version: was bumped and BOTH changelogs got their rows
✓ The lint results (all 7 authoring rules, including the two machine-surface
  parity/ordering checks and the internal-skill discovery-exclusion check)
  were reported
✓ The git add + commit command block is printed as the ABSOLUTE last output

About to end the turn with any box unchecked? The turn is NOT done — complete the missing box first.

When to use

After any edit to one or more skills/<name>/SKILL.md files in this repo, before committing. Handles the full documentation surface so nothing drifts.

Step 0 — Orientation

This skill is specific to the agentic-workflow repository. Before doing anything, confirm you are in that repo (presence of skills/ + CHANGELOG.md

  • CHANGELOG.md). If not, stop and tell the user.

Versioning policy (from CHANGELOG.md):

Bump When
major rename, removed/renamed flag, changed contract or output shape — ships with a migration note
minor new backward-compatible capability: new flag, new section, new routing case
patch wording, examples, clarifications, internal tidy — no behavior change

Process

Progressive loading

The reference allowlist is exactly the two paths below. After orientation:

  1. Read change discovery and authoring lint.
  2. For every discovered skill, read version and documentation sync.
  3. Then print the summary below.

Both resources are normative and one hop from this file. Missing resource → stop; never guess a bump or skip a synchronization surface.

10. Print a summary and the next step

Print a table:

skill              old → new        bump
─────────────────────────────────────────
execute-phase      1.2.0 → 1.3.0   minor
plan-fix           1.0.1 → 1.0.2   patch

Then print the next step:

All documentation updated. Stage and commit:

git add skills/<name>/SKILL.md CHANGELOG.md README.md
git commit -m "chore(skills): bump <name> to <version> — <one-line reason>"

If this is a major bump with a migration note, also add docs/workflow/MIGRATION.md.

Guardrails

  • Never change anything in a SKILL.md except the version: line.
  • Never commit or push — this skill only edits files.
  • If a skill file is not tracked by git (new file not yet added), note it and still update the SKILL.md version and CHANGELOG entries, but warn that the diff-based bump analysis is unavailable for untracked files — ask the user what changed.
  • For the README cells, prefer updating over rewriting: keep the existing tone and length; change only what is factually wrong or missing.

Portability (agents other than Claude Code)

This skill is repo-maintenance for agentic-workflow itself, but the repo may be worked on from any agent:

  • No slash-command menu — follow this SKILL.md directly after editing any skill, before committing.
  • No per-skill model:/effort: — a mid-tier model is enough; this is mechanical version/changelog bookkeeping.

Relationship to other skills

  • Run after any manual edit to a skill or after execute-phase touches a skill file, and before the commit.
  • CLAUDE.md section "Version every change" is the policy this skill enforces mechanically.
  • Major bumps that introduce renames feed into docs/workflow/MIGRATION.md, which init-workspace reads when installing.

Done when

  • Every modified skill's version: field is updated.
  • CHANGELOG.md has a new row for every bumped skill, newest first.
  • The README.md skills and model tables are accurate.
  • Major bumps have a migration note and cross-reference updates.
  • Any authoring-rule violations (missing → Next: block, S1/"Step" phase labels, a user-invocable: true skill absent from plugin.json, a non-alphabetical machine surface) are reported for the user to fix before committing.
  • The next step is printed — the git add + git commit command, ready to run.
Files (agentic-workflow)
  • references
    • DISCOVERY_AND_LINT.md 1.7 KB
      ## Change discovery and authoring lint
      
      ### 1. Identify changed skills
      
      Union modified `skills/*/SKILL.md` paths from `git diff --name-only HEAD` and
      `git diff --cached --name-only`. Explicitly named skills override that set after
      their files are verified. Empty set → report and stop.
      
      ### 2. Choose each bump from its diff
      
      Read `git diff HEAD -- skills/<name>/SKILL.md` (plus `--cached` when staged):
      
      - **major** — rename, removed/renamed flag, or fundamental contract/output change;
      - **minor** — backward-compatible capability, flag, section, or route;
      - **patch** — wording, example, formatting, or internal clarification.
      
      Ask one consolidated question only when a bump remains genuinely ambiguous.
      
      ### 3. Lint, warn, never repair
      
      Check all seven `CLAUDE.md` invariants. This skill may edit only `version:` in a
      SKILL.md, so report violations without fixing them:
      
      1. User-facing entrypoint contains a visible closing `→ Next:` block.
      2. Planning/execution uses `P1…` phases, never `S1` or `Step N`.
      3. Every user-facing skill contains `## Portability`.
      4. Every user-facing skill opens with `## Turn contract`.
      5. Every user-facing skill directory appears as `./skills/<name>` in
         `.claude-plugin/plugin.json`.
      6. That plugin array and `docs/workflow/model-routing.yml` top-level keys are
         alphabetical (compare each ordered list with its sorted form).
      7. A `user-invocable: false` skill absent from the plugin array has anchored
         `metadata.internal: true` inside frontmatter. Plugin-listed internal steps
         are exempt. Check only between the first two `---` lines; body prose does not
         satisfy the rule.
      
      Report every result in the summary; lint warnings do not block the bump.
      
    • VERSION_AND_DOCS.md 1.4 KB
      ## Version and documentation synchronization
      
      ### 1. Bump `version:` only
      
      Parse the frontmatter semver and apply the selected bump, resetting lower
      components (`1.2.3` → patch `1.2.4`, minor `1.3.0`, major `2.0.0`). Replace only
      the `version:` line.
      
      ### 2. Synchronize the changelog
      
      Insert the newest row first in the skill table under `## Per-skill version
      history` in `CHANGELOG.md`:
      
      ```
      | <new-version> | <YYYY-MM-DD> | <bump-type> | <one-sentence summary> |
      ```
      
      For a new skill, create this table in the correct user-facing/internal section:
      
      ```markdown
      #### `<name>`
      | Version | Date | Type | What changed |
      |---|---|---|---|
      | <new-version> | <YYYY-MM-DD> | — | First versioned release |
      ```
      
      Use today's date and a tight behavioral summary. Add or merge today's Release
      log line.
      
      ### 3. Synchronize READMEs and model routing
      
      - Minor/major behavior change: update only the affected Skills-table cell in
        `README.md`. Patch: edit only if the cell is inaccurate.
      - Tier change: update `docs/workflow/model-routing.yml`, then mirror it in both
        README model tables. Never edit the derived `claude` branch directly.
      - Otherwise leave README content unchanged.
      
      ### 4. Handle major migrations
      
      For a rename or removed/renamed flag, append the migration to
      `docs/workflow/MIGRATION.md` (create its standard header when absent), update
      the `CLAUDE.md` skill entry when its name/contract changed, and update stale
      cross-references found under `docs/` and `skills/`.
      
  • SKILL.md 4.5 KB
    ---
    name: bump-skill
    user-invocable: false
    version: 2.3.3
    metadata:
      internal: true
    description: >
      Internal agentic-workflow maintenance: after SKILL.md edits, bump semver,
      lint authoring rules, and synchronize changelogs, READMEs, routing metadata,
      and migrations. Triggers: "bump the skill", "update the changelog",
      "version bump".
    ---
    
    ## Turn contract — verify before ending the turn
    
    ```
    ✓ Every changed skill's version: was bumped and BOTH changelogs got their rows
    ✓ The lint results (all 7 authoring rules, including the two machine-surface
      parity/ordering checks and the internal-skill discovery-exclusion check)
      were reported
    ✓ The git add + commit command block is printed as the ABSOLUTE last output
    ```
    
    About to end the turn with any box unchecked? The turn is NOT done — complete
    the missing box first.
    
    ## When to use
    
    After any edit to one or more `skills/<name>/SKILL.md` files in this repo,
    before committing. Handles the full documentation surface so nothing drifts.
    
    ## Step 0 — Orientation
    
    This skill is **specific to the `agentic-workflow` repository**. Before doing
    anything, confirm you are in that repo (presence of `skills/` + `CHANGELOG.md`
    + `CHANGELOG.md`). If not, stop and tell the user.
    
    Versioning policy (from `CHANGELOG.md`):
    
    | Bump | When |
    |---|---|
    | **major** | rename, removed/renamed flag, changed contract or output shape — ships with a migration note |
    | **minor** | new backward-compatible capability: new flag, new section, new routing case |
    | **patch** | wording, examples, clarifications, internal tidy — no behavior change |
    
    ## Process
    
    ### Progressive loading
    
    The reference allowlist is exactly the two paths below. After orientation:
    
    1. Read [change discovery and authoring lint](references/DISCOVERY_AND_LINT.md).
    2. For every discovered skill, read [version and documentation sync](references/VERSION_AND_DOCS.md).
    3. Then print the summary below.
    
    Both resources are normative and one hop from this file. Missing resource → stop;
    never guess a bump or skip a synchronization surface.
    
    ### 10. Print a summary and the next step
    
    Print a table:
    
    ```
    skill              old → new        bump
    ─────────────────────────────────────────
    execute-phase      1.2.0 → 1.3.0   minor
    plan-fix           1.0.1 → 1.0.2   patch
    ```
    
    Then print the next step:
    
    > All documentation updated. Stage and commit:
    > ```
    > git add skills/<name>/SKILL.md CHANGELOG.md README.md
    > git commit -m "chore(skills): bump <name> to <version> — <one-line reason>"
    > ```
    > If this is a major bump with a migration note, also add `docs/workflow/MIGRATION.md`.
    
    ## Guardrails
    
    - **Never change anything in a SKILL.md except the `version:` line.**
    - **Never commit or push** — this skill only edits files.
    - If a skill file is not tracked by git (new file not yet added), note it and
      still update the SKILL.md version and CHANGELOG entries, but warn that the
      diff-based bump analysis is unavailable for untracked files — ask the user
      what changed.
    - For the README cells, prefer updating over rewriting: keep the existing tone
      and length; change only what is factually wrong or missing.
    
    ## Portability (agents other than Claude Code)
    
    This skill is repo-maintenance for `agentic-workflow` itself, but the repo may
    be worked on from any agent:
    
    - **No slash-command menu** — follow this `SKILL.md` directly after editing any
      skill, before committing.
    - **No per-skill `model:`/`effort:`** — a mid-tier model is enough; this is
      mechanical version/changelog bookkeeping.
    
    ## Relationship to other skills
    
    - Run after any manual edit to a skill or after `execute-phase` touches a
      skill file, and before the commit.
    - `CLAUDE.md` section "Version every change" is the policy this skill
      enforces mechanically.
    - Major bumps that introduce renames feed into `docs/workflow/MIGRATION.md`,
      which `init-workspace` reads when installing.
    
    ## Done when
    
    - Every modified skill's `version:` field is updated.
    - `CHANGELOG.md` has a new row for every bumped skill, newest first.
    - The `README.md` skills and model tables are accurate.
    - Major bumps have a migration note and cross-reference updates.
    - Any authoring-rule violations (missing `→ Next:` block, `S1`/"Step" phase labels,
      a `user-invocable: true` skill absent from `plugin.json`, a non-alphabetical
      machine surface) are reported for the user to fix before committing.
    - **The next step is printed** — the `git add` + `git commit` command, ready
      to run.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related