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 linking detailed rationale and progress to…
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 needs to decide how many commits to make, which files belong…
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), and git-trace (follow historical evolution).
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 user explicitly asks to initialize installed project memory.…
A workflow guide for research-focused Python projects. It covers data processing, regression analysis, diagnostics, tests, result tables, and matplotlib charts.
Review memory needs at a completed work unit and, after user confirmation or an explicit maintenance request, update project memory as one coherent batch. Preserve detailed evidence and searchable history. Do not write memory after every small edit or use handoffs to bypass a user's deferral.
A research-project scaffold that defines what belongs in project folders, research materials, and shared project memory.
★not rated 5 1mo agoA59 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: