Prepare an AI-Q Pull Request
Use this skill to take a finished AI-Q change from a working branch to a
review-ready pull request: a focused branch off develop, DCO-signed commits,
the PR template filled with real validation evidence, and the copy-pr-bot CI
flow followed correctly.
Start Here
- Confirm the change is scoped: no unrelated files, no generated artifacts, no
secrets, no environment-specific hostnames.
- Confirm validation already ran. This skill does not invent test commands —
run
aiq-release-qa first and reuse its exact output as evidence.
- Confirm every commit is signed off (DCO). Commits without a
Signed-off-by
trailer may be rejected.
- Target the
develop branch unless a maintainer asked for a release branch.
Authoritative References
- CONTRIBUTING.md: the canonical PR workflow, Local
Validation, DCO text, and the copy-pr-bot /
/ok to test / /merge flow.
- .github/pull_request_template.md:
the exact sections and checklist your PR description must fill.
- AGENTS.md: "Git and PR hygiene" and the validation
commands
aiq-release-qa runs.
For the step-by-step checklist and the bot command reference:
- references/pr-checklist.md
Workflow
- Verify the branch is focused and based on
develop; rebase or reset scope if
unrelated files crept in.
- Ensure every commit is signed:
git commit -s (and git commit --amend -s
or git rebase --signoff to fix unsigned commits already made).
- Run the relevant checks via
aiq-release-qa and keep the exact output.
- Push the branch and open the PR into
develop.
- Fill the PR template: Overview, Validation (paste the commands and output),
reviewer starting point, related issues, and tick every checklist box you
can honestly tick.
- Drive CI: a maintainer or vetter comments
/ok to test, copy-pr-bot mirrors
the PR to pull-request/<number>, and CI runs there.
- Address review feedback until required checks and code-owner review pass.
Validation
This skill is about PR hygiene, not code execution; verify the contributor
mechanics:
git log --pretty=full origin/develop..HEAD | grep -c "Signed-off-by:" # every commit signed
git diff --name-only origin/develop..HEAD # only intended files
git status --porcelain # no stray artifacts
Expected: the sign-off count equals your commit count, the changed-file list
contains only files relevant to this change, and the working tree is clean.
Common Mistakes
- Unsigned commits. Use
git commit -s; fix existing ones with
git rebase --signoff origin/develop before pushing.
- A vague Validation section. Paste the real commands and their output from
aiq-release-qa; "ran tests" is not evidence.
- Scope creep: unrelated refactors, formatting churn on untouched files, or
committed generated artifacts.
- Committing secrets or
deploy/.env values. Resolve secrets at runtime; never
paste them into the PR.
- Expecting CI to run on push alone — it runs on the copy-pr-bot mirror after
/ok to test.
- Skipping the docs update for user-facing or contributor-facing changes.
Related Skills
aiq-release-qa
aiq-add-tool
aiq-add-data-source
1---2name: aiq-prepare-pr3description: Use when preparing, opening, or updating an AI-Q pull request — scoping the branch, signing commits with DCO, filling the PR template with real validation evidence, and following the copy-pr-bot CI and merge flow.4license: Apache-2.05compatibility: Claude Code, Codex, Cursor, OpenCode, and Agent Skills-compatible tools.6metadata:7 source: https://skillmd.com/skills/nvidia-ai-blueprints-aiq/aiq-prepare-pr8 version: "0.1.0"9 source-repo: "NVIDIA-AI-Blueprints/aiq"10 tags: "aiq pull-request dco contributing release-qa"11allowed-tools: Read Bash Edit12---1314# Prepare an AI-Q Pull Request1516Use this skill to take a finished AI-Q change from a working branch to a17review-ready pull request: a focused branch off `develop`, DCO-signed commits,18the PR template filled with real validation evidence, and the copy-pr-bot CI19flow followed correctly.2021## Start Here2223- Confirm the change is scoped: no unrelated files, no generated artifacts, no24 secrets, no environment-specific hostnames.25- Confirm validation already ran. This skill does not invent test commands —26 run `aiq-release-qa` first and reuse its exact output as evidence.27- Confirm every commit is signed off (DCO). Commits without a `Signed-off-by`28 trailer may be rejected.29- Target the `develop` branch unless a maintainer asked for a release branch.3031## Authoritative References3233- [CONTRIBUTING.md](../../../CONTRIBUTING.md): the canonical PR workflow, Local34 Validation, DCO text, and the copy-pr-bot / `/ok to test` / `/merge` flow.35- [.github/pull_request_template.md](../../../.github/pull_request_template.md):36 the exact sections and checklist your PR description must fill.37- [AGENTS.md](../../../AGENTS.md): "Git and PR hygiene" and the validation38 commands `aiq-release-qa` runs.3940For the step-by-step checklist and the bot command reference:4142- [references/pr-checklist.md](references/pr-checklist.md)4344## Workflow45461. Verify the branch is focused and based on `develop`; rebase or reset scope if47 unrelated files crept in.482. Ensure every commit is signed: `git commit -s` (and `git commit --amend -s`49 or `git rebase --signoff` to fix unsigned commits already made).503. Run the relevant checks via `aiq-release-qa` and keep the exact output.514. Push the branch and open the PR into `develop`.525. Fill the PR template: Overview, Validation (paste the commands and output),53 reviewer starting point, related issues, and tick every checklist box you54 can honestly tick.556. Drive CI: a maintainer or vetter comments `/ok to test`, copy-pr-bot mirrors56 the PR to `pull-request/<number>`, and CI runs there.577. Address review feedback until required checks and code-owner review pass.5859## Validation6061This skill is about PR hygiene, not code execution; verify the contributor62mechanics:6364```bash65git log --pretty=full origin/develop..HEAD | grep -c "Signed-off-by:" # every commit signed66git diff --name-only origin/develop..HEAD # only intended files67git status --porcelain # no stray artifacts68```6970Expected: the sign-off count equals your commit count, the changed-file list71contains only files relevant to this change, and the working tree is clean.7273## Common Mistakes7475- Unsigned commits. Use `git commit -s`; fix existing ones with76 `git rebase --signoff origin/develop` before pushing.77- A vague Validation section. Paste the real commands and their output from78 `aiq-release-qa`; "ran tests" is not evidence.79- Scope creep: unrelated refactors, formatting churn on untouched files, or80 committed generated artifacts.81- Committing secrets or `deploy/.env` values. Resolve secrets at runtime; never82 paste them into the PR.83- Expecting CI to run on push alone — it runs on the copy-pr-bot mirror after84 `/ok to test`.85- Skipping the docs update for user-facing or contributor-facing changes.8687## Related Skills8889- `aiq-release-qa`90- `aiq-add-tool`91- `aiq-add-data-source`