菜单
koopa release procedure — CHANGELOG authoring, bumpver contract, pre-release gate, and what stays with the user. Use when preparing a release, writing release notes, or understanding what "prepare the release" entails.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | koopa-release |
| description | koopa release procedure — CHANGELOG authoring, bumpver contract, pre-release gate, and what stays with the user. Use when preparing a release, writing release notes, or understanding what "prepare the release" entails. |
bumpver is configured in pyproject.toml with tag = false, push = false,
commit = true. Running bumpver update (or equivalent) bumps two lines in
pyproject.toml:
version = "<pep440>" (no v prefix)current_version = "v<version>" (with v prefix)It creates a single commit Bump version to vX.Y.Z. — no tag, no push.
Tagging, pushing, and merging develop→main are always the user's job.
bumpver (the Bump version to vX.Y.Z.
commit). Confirm pyproject.toml:3 reads the new version.## koopa X.Y.Z (...) heading. See format below.pytest lang/python/tests/
ruff check lang/python/src/
ruff format --check lang/python/src/
pyright lang/python/src/
git tag vX.Y.Z, git push origin develop,
git push origin vX.Y.Z, merge develop→main via PR.File: CHANGELOG.md at the repo root.
Section heading: ## koopa X.Y.Z (YYYY-MM-DD)
v prefix.## heading and the first subsection heading.Subsections (in order, omit if empty):
Major changes: — substantive user-facing changes, ~4-6 bullets.Minor changes: — small fixes, housekeeping, version bumps.New apps: — only present when new top-level keys were added to
etc/koopa/app.json this cycle. Verify with:
git diff vPREV..HEAD -- etc/koopa/app.json | grep -E '^\+ "[a-z]'Bullet style: - list, wrapped at ~80 columns, two-space continuation indent.
Match the style of the surrounding entries exactly.
Previous release tag: find the prior Bump version to vX.Y.Z. commit or the
existing vPREV git tag. The range is vPREV..HEAD (or PREV_BUMP_SHA..HEAD
if the tag hasn't been created yet for the previous release).
Prepare release housekeeping commits.New apps: entries: name, version, one-line description, default/non-default.pyproject.toml:3 — version = "X.Y.Z". Read at runtime by
koopa_version() in lang/python/src/koopa/version.py. No other file
hardcodes the koopa version.
Acid Genomics R package development conventions — per-project air.toml, global ~/.lintr only, roxygen2 8.x @importFrom split, S4 linter tuning, AcidDevTools::check() gate. Use when writing or checking an acidgenomics R package, configuring air/lintr, or fixing roxygen/lint failures.
koopa R package release — cloud-native S3 + CloudFront, acidgenomics profile, koopa app r publish/reindex/archive, sonoma-arm64 binaries, pre-release AcidDevTools::check() gate. Use when releasing, publishing, reindexing, or archiving an Acid Genomics R package.
PowerShell (pwsh 7+) activation architecture, starship integration, and color-mode sync in koopa. Use when writing or debugging lang/powershell/ files, editing activate-*.ps1 functions, adding prompt-tool support (starship, zoxide), integrating OS appearance detection, or porting shell logic from bash/zsh/fish to PowerShell.
koopa AWS environment configuration — the gitignored <koopa-root>/.env, load_dotenv()/aws_account_id()/koopa_s3_bucket() helpers in aws.py, required vars, bucket naming, lazy-eval rule. Use when adding an AWS secret, wiring a bucket/CloudFront ID, or debugging a missing AWS env var in release tooling.
How koopa manages home dotfiles via chezmoi — source-of-truth layout, the explicit --source flag, template-vs-generator ordering, XDG path derivation in templates, symlink_ source files for App Support bridges, diagnosing chezmoi status contamination from stale env, and the correct re-run command. Use when editing a dotfile, working in opt/dotfiles/chezmoi/, debugging a file that reverts on chezmoi apply, wiring a chezmoi template, or bridging XDG paths to macOS Library/Application Support.
How koopa propagates and applies dark/light color mode across SSH, tmux, shells, and chezmoi-rendered theme files. Use when debugging wrong-palette or stale-theme symptoms after a dark↔light flip, working on color-mode sync jobs or watchers, editing the chezmoi color-mode apply path, or investigating why bat/starship/delta renders the wrong theme while fzf/LS_COLORS look correct.