Read the uncommitted diff in dynamic-neural-field-composer and print conventional commit message(s) for it, grouped by logical change. Use when asked to write, suggest or draft a commit message, or "what should I commit this as".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Reads the working tree and prints commit messages to chat. Never runs git add or
git commit - staging and committing stay a human decision.
git status --short
git diff HEAD
Include untracked files - git status --short marks them ??; read their contents too,
they are not in git diff HEAD by default.
If the tree is clean, say so and stop. Do not invent a message for nothing.
A diff touching three unrelated things gets three messages, not one. Group by concern: a rename here, a new skill there, a doc fix elsewhere - even if they landed in the same session. Do not force unrelated work into a single commit to keep the list short.
Per .claude/CLAUDE.md > Naming - use what the project actually uses, not a generic
convention:
fix, feat, test, perf, docs, refactor, ci, chore, style, plus release:
for version bumps.type(scope): summary.bug/, but their commits use fix: - never bug:.fix: reject 1D<->2D connections with matching flattened size
test(golden): add sigmoid regime coverage
chore: pin vcpkg and imgui-platform-kit revisions
A markdown bullet list, one message per logical change, each in a code span. When there is more than one, name the files it covers so they can be staged separately:
- `refactor: rename (project)notes to notes` - .gitignore, .claude/CLAUDE.md, wiki/Helping Claude Help You.md
- `feat: add /commit and /pr skills` - .claude/skills/commit/SKILL.md, .claude/skills/pr/SKILL.md
Nothing else - no staging, no committing, no pushing.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Orchestrate unattended resolution of open GitHub issues - triage by complexity, dispatch parallel worker agents into isolated worktrees, review their diffs, open PRs, and monitor CI and CodeRabbit until green. Use when asked to work through open issues autonomously or put Claude on auto-pilot.
The English summary is being prepared. Showing the original description.
Configure, build and test dynamic-neural-field-composer. Use whenever you need to compile the library, run the GoogleTest suite, verify a change builds, or reproduce a test failure.
The English summary is being prepared. Showing the original description.
Verify documentation keeps up with a code change in dynamic-neural-field-composer - Doxygen on public API, the matching wiki page, and stale references elsewhere. Use before opening a PR, or when asked whether docs need updating.
The English summary is being prepared. Showing the original description.
Check a change for performance regression against this machine's recorded baseline - decide whether the diff needs checking, run the deck benchmark under the hygiene wrapper, and attribute any regression to an element. Use before opening a PR that touches the simulation hot path.
The English summary is being prepared. Showing the original description.
Read the branch diff in dynamic-neural-field-composer and print a PR title and description in chat, filling the repo's pull request template. Use when asked to write, draft or suggest a PR title/description, or "what should the PR say".
The English summary is being prepared. Showing the original description.
Review a diff against dynamic-neural-field-composer's own standards - backwards compatibility, Clean Code, tools/ helper reuse, C++20 idiom, hot-path performance, and test coverage. Use before opening a PR or when asked to review a branch or change.
The English summary is being prepared. Showing the original description.