minor

A planning command for preparing a minor software release from the changes made since the previous version tag. A version tag is a Git label marking a released point in the code history.

In plain words
What is it for?
Use it to review unreleased commits, compare them with the project roadmap, suggest any missing follow-up work, and draft a release issue after confirmation.
Why use it?
It turns accumulated changes into a clear release summary and checks which project milestone they represent, without changing files or publishing anything.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/awesome-embedded-learning-studio/tutorial_awesomemoderncpp/minor
Clone the repo
git clone --depth 1 https://github.com/Awesome-Embedded-Learning-Studio/Tutorial_AwesomeModernCPP

Made for: Claude Code.

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 903 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.00903
Opus 5 $0.00023 $0.00451
Sonnet 5 $0.00009 $0.00181
Haiku 4.5 $0.00005 $0.00090

Measured 2d ago against content hash 1d028cda1c56, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

minor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/minor.md · 60 lines

What it actually says

/minor — 发版打包规划(规划者模式)

你现在是规划者,不是执行者。本轮你不修改任何文件、不建 tag、不碰版本号、不调 gh

定位

Minor = 发版打包规划:把自上次 tag 以来累积的全部 patch(所有类型)捆成一次 release,讲清楚这次发版做了什么、到了哪个里程碑。

关键:内容推进本身是 patch 级工作(每写一段内容都是一个 patch)。minor 不做内容,只在"攒够了、要发版"时由用户手工判定触发,与 patch 类型无关。

输入

$ARGUMENTS —— 本次发版的框定或关注点。为空时由你扫描后给出建议。

流程

1. 扫描累积与路线

  • 累积 patch: 运行 git log $(git describe --tags --abbrev=0)..HEAD --oneline 列出自上次 tag 以来的全部待打包提交。
  • 路线对照: 读 todo/000-project-roadmap.md + 相关 todo/01x-vol*.md,看这批 patch 合起来推进了哪条 next-step。
  • ⚠️ 项目 Python 脚本一律用 .venv/bin/python

2. 框定本次发版

  • 把累积 patch 按类型粗分,给出本次 release 的一句话叙事
  • 对照 volume TODO,说清本次发版到达了哪个内容里程碑。推进是 patch 做的,minor 只负责"看清楚到了哪"。
  • 若离更完整的 minor 还差一点:建议再补哪 1-2 个 patch(留给后续 /patch,不在 minor 里执行)。
  • 保持灵活,不搞死板:讲明白发版范围即可,不强制验收标准、不强制文件清单。

3. 提案 → 讨论 → 确认(核心是讨论)

  • 先用一句话讲清这次发版要打包什么,作为讨论起点(累积统计、里程碑口头带过,别堆列表)。
  • 与用户来回讨论打磨,直到用户明确确认
  • 未确认前,不产出 Issue。

4. 确认后,产出两样东西到聊天框(讨论的最终产物)

(a) 本轮确认的发版工作 —— 一句话总结聊定的发版范围与里程碑。

(b) 迭代 Issue(Markdown) —— 套用 .claude/templates/iteration-issue.md(极简版),迭代类型填 minor。用 ```markdown 代码块包裹。用户微调后自行送 GitHub。

(a)(b) 都必须通俗易懂:用大白话写,少术语、别堆结构化清单,让没参与讨论的人也能一眼看懂这次发版干了啥。

输出后停下。

硬约束

  • ❌ 不直接执行任何文件修改。只产出讨论结果。
  • ❌ 不碰版本 bump / CHANGELOG / git tag(用户自理)。
  • 不调 gh issue create,不开 issue
  • ✅ 全程讨论驱动;Issue 仅在用户确认后产出。
  • 输出通俗易懂:用大白话写,别堆术语。
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 60 lines · 45 tokens per session scan A 1d028cda1c56

Subscribe to this mod's changes

minor is a command published in the GitHub repository Awesome-Embedded-Learning-Studio/Tutorial_AwesomeModernCPP (250 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 903 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.