Add pr-best-practices skill#504
Open
Thanhphan1147 wants to merge 7 commits intomainfrom
Open
Conversation
- .github/skills/pr-best-practices/SKILL.md: skill that analyzes merged LLM-authored PRs, compares first vs final commit, and synthesizes do/don't rules with concrete code examples into best-practices.instructions.md - .github/skills/pr-best-practices/evals/evals.json: 3 eval cases covering substantive PR, validation-fix PR, and trivial (non-significant) PR - .github/instructions/best-practices.instructions.md: initial rules extracted from PR #475 (relation contracts, reconcile flow, testing) and PR #500 (validation error handling) with before/after code examples - .gitignore: ignore *-workspace/ directories (skill eval scratch data) Co-authored-by: Copilot <[email protected]>
- Clarify description: 'after human reviews and code changes' (was 'after human review') - Replace generic file extension list with explicit repo-aware globs: **/*.py (charm/test code), haproxy-operator/*.j2 (HAProxy templates), **/*.yaml (charmcraft/snapcraft manifests) - Drop .github/workflows/*.yaml — CI config doesn't yield coding best practices - Fix typo **/*yaml → **/*.yaml; strip trailing whitespace Co-authored-by: Copilot <[email protected]>
Contributor
Test results for commit 4289e39Test coverage for 4289e39 Static code analysis report |
Contributor
Test results for commit 4289e39Test coverage for 4289e39 Static code analysis report |
Contributor
Test results for commit 4289e39Test coverage for 4289e39 Static code analysis report |
Contributor
Test results for commit 4289e39Test coverage for 4289e39 Static code analysis report |
Contributor
Test results for commit 4289e39Test coverage for 4289e39 Static code analysis report |
alithethird
approved these changes
May 7, 2026
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
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.
What this PR does
Add a skill that when called will analyze the changes between the first and final iteration of a PR authored by an LLM. The result is a set of good and bad example maintained in
.github/instructions/best-practices.instructions.md. For example:Do
_reconcile— relation data can exist before the snap service is ready to answer requests (PR #475)Before review — refresh happened unconditionally during reconcile
After review — only refresh when the service is actually running
Checklist
docs/changelog.mdwith user-relevant changesdocs/release-notes/artifacts. If no change artifact is necessary, I tagged the PR with the labelno-release-note.(e.g., in
.github/workflows/integration_tests.yaml, ensure themoduleslist is correct)terraform fmtpasses andtflintreports no errors