docs(finishing-a-development-branch): check repo PR templates before creating PR#1842
Open
citizen204 wants to merge 1 commit into
Open
docs(finishing-a-development-branch): check repo PR templates before creating PR#1842citizen204 wants to merge 1 commit into
citizen204 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When using
finishing-a-development-branchto create a PR (Option 2), the skill did not guide the agent to check for a repository PR template before drafting the PR body. Many repositories use PR templates to enforce required process fields (testing evidence, issue links, risk notes, etc.), so skipping the template check can produce a PR that violates project contribution standards.Fixes #1834
Changes
skills/finishing-a-development-branch/SKILL.md: Add a PR template lookup step inside Option 2 covering all GitHub-supported template locations, with rules for single template, multiple templates, missing required information, and no-template fallback.