diff --git a/.agents/skills/commit/SKILL.md b/.agents/skills/commit/SKILL.md index 5d9923b5eed..32e81bf21e7 100644 --- a/.agents/skills/commit/SKILL.md +++ b/.agents/skills/commit/SKILL.md @@ -36,9 +36,7 @@ invent one.** is the user's DCO certification of changes they have reviewed: never commit with `-s` work the user has not seen. 6. Add new commits rather than amending pushed ones, and never force-push - unless the user asks or the branch is being rebased. PRs are squash-merged, - so the branch history costs nothing on `main` and shows reviewers the - decision chain. + unless the user asks or the branch is being rebased. 7. If the branch has an upstream (`git rev-parse --abbrev-ref @{u}`), push. 8. If the branch has an open PR (`gh pr view --json state,body`), update its description with `gh pr edit --body` when the commit changes what the diff --git a/.agents/skills/pr/SKILL.md b/.agents/skills/pr/SKILL.md index 96de3e016d6..967066ab1e6 100644 --- a/.agents/skills/pr/SKILL.md +++ b/.agents/skills/pr/SKILL.md @@ -23,8 +23,8 @@ footers. Disclose AI assistance as the last line of the PR body, italicized: bumps, docs, ROMFS). Build with the `build-px4-linux` or `build-px4-macos` skill. Fix any build errors before opening the PR. 4. PR **title:** `type(scope): description` — under 72 chars, covers the - overall change across all commits. This becomes the squash-merge commit - message. + overall change across all commits. If a maintainer squash-merges the PR, + this becomes the commit message. 5. PR **body:** as short as it can be while still landing the point — a reviewer should take it in at a glance, and a long description is one nobody reads. Sections, in order: `## Summary`, `## Problem`,