원클릭으로 Manus에서 모든 스킬 실행

version-bump

스타110

포크6

업데이트2026년 5월 6일 11:11

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".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

agentculture

agentculture/culture

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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; culture/__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.

이 저장소의 다른 Skills

같은 저장소

run-tests

agentculture/culture

Run pytest with parallel execution and coverage. Use when running tests, verifying changes, or the user says "run tests", "test", or "pytest".

2026-07-02110

communicate

agentculture/culture

Cross-repo + mesh communication: file tracked GitHub issues on sibling repos, comment on existing issues, fetch issues with body + comments to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside the current repo (a brief for a sibling-repo agent, a status ping for a Culture channel, pulling an issue body for context). Issue I/O is backed by `agtag` (>=0.1); agtag auto-signs from the local `culture.yaml`. Mesh messages are unsigned (the IRC nick is the speaker).

2026-07-02110

culture

agentculture/culture

Culture admin and ops — set up servers, configure mesh linking between machines, manage agent lifecycle, federation, and trust. Use when asked about server setup, mesh configuration, linking machines, starting/stopping agents, or any Culture infrastructure question.

2026-07-02110

recall

agentculture/culture

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope culture --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via this s

2026-07-02110

remember

agentculture/culture

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope culture --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save to memo

2026-07-02110

ask-colleague

agentculture/culture

Ask colleague — a *different* backend/model than you (e.g. a local vLLM Qwen) — to take a scoped repo task off your plate, then fold its answer back. The point isn't a stronger model; it's a second, independent mind, and that diversity is the value: `ask-colleague review` gets a candid second opinion on a diff, `ask-colleague explore` gets a fresh read of an area, `ask-colleague write` hands off a small implementation, `ask-colleague feedback` grades a finished work item (the ROI loop), and `ask-colleague clean` reaps stale/corrupt `colleague/*` branches a crashed run left behind (which can break `git fetch`). Reach for it REFLEXIVELY, the way you'd lean over to the teammate at the next desk — not only when asked: before you present or open a PR on a non-trivial committed diff, run `review` for a diverse second opinion; for a fresh read of an unfamiliar area whose answer is independent of your current context, run `explore`. Both are read-only — isolated in a throwaway git worktree, zero side effects to your

2026-06-13110

name	version-bump
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".

Version Bump

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; culture/__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.