Skip to content
cccskills
FreePublished on GitHub

pr

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.

Works withGitHub
See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

PR

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.

1. Read the branch

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.

2. Title

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.

3. Body - fill the existing template

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.

4. Issue number

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.

Output

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

Jgocunha/dynamic-neural-field-composer19Updated Oct 9, 2026

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.

Jgocunha/dynamic-neural-field-composer19Updated Oct 9, 2026

commit

Free

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.

Jgocunha/dynamic-neural-field-composer19Updated Oct 9, 2026

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.

Jgocunha/dynamic-neural-field-composer19Updated Oct 9, 2026

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.

Jgocunha/dynamic-neural-field-composer19Updated Oct 9, 2026

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.

Jgocunha/dynamic-neural-field-composer19Updated Oct 9, 2026

See all skills by Jgocunha

Report a problem with this skill