Generate structured git commit messages for staged changes using Conventional Commits plus `Why`/`What`/`Risk`/`Tests` sections. Use when preparing a commit after code changes, especially in repositories that keep living docs under `memory-docs/`. Prefer…
Orchestrate a complete commit flow: use commit-planner to define batches, stage the selected batch, generate the message with commit-messages, and execute git commit safely.
Analyze staged, unstaged, and untracked changes; group them into functionally coherent commit batches; and recommend staging order, commit boundaries, and related memory-docs references. Use when the working tree contains multiple kinds of changes and Codex…
Use at the start of a conversation to establish repository context, or when the user asks to review code changes, compare branches, or trace file and line history. Covers three directions: git-scan (repo overview), git-review (understand a concrete change),…
Initialize or migrate an installed memory-docs system from repository evidence. Use after memory-docs templates are installed but still contain placeholders, when existing briefs, plans, notes, and docs must be distilled into the standard layers, or when a…
用于本仓库及类似研究型 Python 项目中的数据处理、回归、诊断、测试与绘图任务。涉及 Python 脚本、回归分析、结果表、诊断脚本、数据读取、matplotlib 绘图时使用。提供路径规范、测试先行、轻量预览、结果输出和环境选择约定。
Maintain an initialized memory-docs system after meaningful implementation, research, operational, documentation, decision, milestone, or handoff work. Use when verified durable facts or continuation context should be distilled into canonical owners, or when…