AGENT SKILL

version-bump

Bump the semver version in pyproject.toml (major, minor, or patch) and prepend a Keep-a-Changelog entry to CHANGELOG.md. Use when preparing a release, before creating a PR (the version-check CI job blocks merge if you don't), or when the user says "bump version", "release", or "increment version".

License 许可
Apache-2.0
最近更新
2026-09-29
Stars
★ 3
Forks
0

01 前言 Front Matter

name
version-bump
type
command
description
Bump the semver version in pyproject.toml (major, minor, or patch) and prepend a Keep-a-Changelog entry to CHANGELOG.md. Use when preparing a release, before creating a PR (the version-check CI job blocks merge if you don't), or when the user says "bump version", "release", or "increment version".

02 资源文件 1

03 SKILL.md 正文

Version Bump

Bump the semver version in pyproject.toml and prepend a new entry to CHANGELOG.md. Mirrors the AgentCulture workflow used by culture, afi-cli, cfafi, and other org repos; vendored here so the repo is self-contained.

Usage

Run from the repo root.

# With changelog content (pipe JSON via stdin):
echo '{"added":["New X"],"changed":["Refactored Y"],"fixed":["Bug in Z"]}' \
  | python3 .claude/skills/version-bump/scripts/bump.py minor

# Without changelog content (inserts empty ### Added/Changed/Fixed stubs):
python3 .claude/skills/version-bump/scripts/bump.py patch

# Check current version without bumping:
python3 .claude/skills/version-bump/scripts/bump.py show

Bump Types

Type Example When to use
major 0.1.0 → 1.0.0 Breaking changes, namespace restructures, CLI surface breaks
minor 0.1.0 → 0.2.0 New features, new commands, new modules
patch 0.1.0 → 0.1.1 Bug fixes, doc updates, dependency bumps, CI-only changes
show prints 0.1.0 Read-only — no files changed

Changelog JSON Format

Pass via stdin. All fields are optional — only non-empty sections are rendered.

{
  "added":   ["List of new features"],
  "changed": ["List of changes to existing functionality"],
  "fixed":   ["List of bug fixes"]
}

What it touches

  • pyproject.toml — the version = "x.y.z" field (single source of truth; steward/__init__.py reads it via importlib.metadata, so there's no separate __version__ literal to keep in sync).
  • CHANGELOG.md — inserts a new ## [x.y.z] - YYYY-MM-DD entry at the top.

The script does the rest. Pick a bump type from the diff (patch for fixes, minor for new features, major for breaking changes), summarize the diff into added / changed / fixed lists, pipe as JSON, and commit the resulting pyproject.toml + CHANGELOG.md alongside the code change so the version-check CI job sees a consistent bump.

04 同仓库更多 Skills

agentculture
agentculture/culture-nodes

sample

Fixture skill proving the .qwen/skills leg carries at least one skill.

★ 3
agentculture
agentculture/culture-nodes

sample

Fixture skill proving the .qwen/skills leg carries at least one skill.

★ 3
agentculture
agentculture/culture-nodes

sample

Fixture skill proving the .qwen/skills leg carries at least one skill.

★ 3
agentculture
agentculture/culture-nodes

think

Think a vague feature idea into a buildable spec by working backwards (the idea→spec leg; drives the `devague` CLI). Start from the announcement ("pretend it shipped"), capture and classify claims, interrogate them with honesty conditions and hard questions, park open vagueness as a first-class object, and export a spec only once the frame *converges*. Use when the user says "think this through", "spec this", "work backwards", "turn this idea into a spec", "announcement frame", or "devague", or when a feature request is too vague to build yet. Explore scope first when the idea touches an existing codebase — the sibling `scope` skill is the optional opening leg ahead of `think`. Once a spec exports, hand off to the sibling `spec-to-plan` skill to turn it into a plan. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.

★ 3
agentculture
agentculture/culture-nodes

summarize-delivery

Close the loop after an `assign-to-workforce` run by turning what actually happened into an accountability artifact — planned versus actual delivery, mid-work decisions, plan drift, evidence-backed delivery claims, and remaining work. The plan the user confirmed is the contract; this skill records where execution obeyed it, where it changed, and what is genuinely safe to claim as delivered. Runs on complete, partial, AND failed runs — failure is reported faithfully, never smoothed over. Use when the user says "summarize delivery", "delivery summary", "wrap up", "close the loop", "what did we actually ship", or "plan versus actual", or after `assign-to-workforce` merges (or fails to merge) a plan's waves. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the inbound skills here.

★ 3
agentculture
agentculture/culture-nodes

spec-to-plan

Turn a converged devague spec into a buildable plan by working forwards (the spec→plan leg; drives the `devague plan` CLI group). Seed a plan from a converged frame, add tasks that collectively cover every coverage target (the frame's confirmed claims + honesty conditions), give each task acceptance criteria and an honest dependency order, park genuine unknowns as first-class risks, and export a plan only once it *converges*. Use when the user says "spec to plan", "stp", "turn this spec into a plan", "plan this spec", "make a build plan", or after the `think` skill exports a spec. Authored and maintained in agentculture/devague (origin = devague); guildmaster pulls this skill from here and broadcasts it to the AgentCulture mesh — it is NOT vendored from guildmaster like the other skills here.

★ 3