Skip to content

chore: Add PR creation guidelines to AGENTS.md #698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ValerianRey wants to merge 5 commits into
base: main
Choose a base branch
from
+9 −0
Open

chore: Add PR creation guidelines to AGENTS.md #698

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
458f5ae
chore: Add PR creation guidelines to AGENTS.md
ValerianRey May 20, 2026
d57d423
chore: Use gh label list instead of hardcoded label lists
ValerianRey May 20, 2026
19e23fa
Merge branch 'main' into worktree-improve-claude-md
ValerianRey May 21, 2026
cf00667
Ask agents to make short and efficient pr message
ValerianRey May 21, 2026
14dc52f
Merge branch 'main' into worktree-improve-claude-md
ValerianRey May 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,12 @@
- Prefix protected functions and modules with '_'.
- Always follow SOLID principles when implementing stuff, and in particular the single
responsibility principle and the Liskov substitution principle.
- When creating a pull request, run `gh label list` to discover available labels, then:
- Add the `cc: <type>` label that best describes the change. The CI will use it to
prepend the conventional commit type to the title.
- If the change targets a specific package, also add the matching `package: <scope>`
label.
- If the change introduces a breaking API change, add the `breaking-change` label.
- Keep the title short enough that once the CI prepends `<type>[(<scope>)][!]: ` and
GitHub appends ` (#NNN)` on merge, the total stays under 72 characters.
- The PR message should be short and efficient.
Loading