Skip to content

docs(skill): require roll PRs to note they were skill-generated - #629

Merged
mxschmitt merged 1 commit into
mainfrom
skill/roll-pr-footer
Aug 12, 2026
Merged

docs(skill): require roll PRs to note they were skill-generated#629
mxschmitt merged 1 commit into
mainfrom
skill/roll-pr-footer

Conversation

@mxschmitt

Copy link
Copy Markdown
Owner

While reviewing #628 (a roll PR generated by the roll-playwright skill), it wasn't obvious at a glance that the PR was skill-generated, and the PR body only cited Python and .NET as cross-binding references — Java was skipped, despite Step 1 explicitly requiring all three.

This adds a mandatory footer to the skill's Step 10 PR-creation instructions:

---
🤖 Rolled with the [`roll-playwright`](.claude/skills/roll-playwright/SKILL.md) skill.
Sibling references used: python <PR_URL>, java <PR_URL>, dotnet <PR_URL>
verify-parity.sh (Step 9): <clean | N items flagged and how each was resolved>

This makes future skill-generated rolls identifiable, and doubles as a forcing function for the "check all three siblings" rule.

🤖 Generated with Claude Code

Adds a mandatory footer to roll-playwright's Step 10 PR-creation
instructions identifying the PR as skill-generated, listing the
sibling (python/java/dotnet) reference PRs used, and the
verify-parity.sh outcome. Doubles as a forcing function for the
Step 1 requirement to check all three sibling clients, which PR #628
skipped (only cited python + dotnet).
@mxschmitt
mxschmitt merged commit 7ccb7b1 into main Aug 12, 2026
21 checks passed
@mxschmitt
mxschmitt deleted the skill/roll-pr-footer branch August 12, 2026 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant