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".
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
Reads the branch against origin/main and prints a PR title and body to chat. Never runs
gh pr create or git push - opening the PR stays a human decision.
git branch --show-current
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
If the branch is main, or there are no commits ahead of origin/main, say so and stop.
Same conventional format as a commit - <type>: <lowercase summary>. If the branch's
commits share one type, use it; if they are mixed, pick the dominant concern rather than
concatenating types.
Use .github/pull_request_template.md verbatim as the shape. Do not invent a different
body structure.
## What and why
<2-4 bullets or a short paragraph - what changed, why>
## How to verify
<concrete steps - commands, a named test filter, the `build-and-test` skill>
## Checklist
- [ ] Tests added or updated
- [ ] Doxygen updated (if public API changed)
- [ ] Wiki updated (if user-visible behaviour changed)
- [ ] CI passes (Windows, Linux, macOS)
Tick a checklist box only if it was actually verified this session. Leave the rest unticked - do not tick optimistically.
Look for it in the branch slug or the commit messages. If found, close the body with
Closes #<N>. If not found, do not guess a number - emit the literal placeholder
Closes #<N> and say in your reply that no issue number was found.
A markdown title line, kept outside the fence since gh pr create takes --title and
--body as separate arguments, followed by the filled body inside its own single fenced
code block (```markdown) so the body renders as literal, copy-pasteable text rather
than being rendered as chat formatting - ready to paste into gh pr create --body.
Nothing else - no push, no gh pr create.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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".
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。