chore: add commit format enforcement and chore vs fix guidance in maintenance skill - #268
Conversation
|
/oc update PR title and description. Especially pr title following conventions, consider pre commit hook for this too |
|
/oc remove line on This is consolidated issue ... |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
PR title updated to Re: pre-commit hook — worth adding but out of scope for this PR. A simple #!/bin/bash
pattern="^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\(.+\))?!?: .+"
if ! head -1 "$1" | grep -qE "$pattern"; then
echo "Commit message must match: $pattern"
exit 1
fiInstall via |
|
/oc add .opencode/ to exception rules of base branch check |
|
Done. Removed the "consolidated issue" line. |
|
/oc rename title and commits. V. Important for maintenance updates to not use fix otherwise it will trigger an accidental auto release Use either chore or fix. Also encode this into the skill to ensure agent remembers this. |
|
Looking at the workflow, NON_CICD_FILES=$(echo "$CHANGED_FILES" | grep -v -E "^(.github/|AGENTS\.md$|pyproject\.toml$|opencode\.json$|opencode\.yaml$|\.opencode/|\.releaserc)" || true)The Is there a specific scenario where it's failing, or were you looking for a different exception? |
|
/oc its failing on this PR? Investigate |
d4386d7 to
e489150
Compare
|
/oc can you make it critical before every git commit and PR title creation ... |
|
Done. Summary:
Both files now explicitly warn agents: using |
|
/oc Specify use chore: or ci: in place of fix: for your new rule added |
|
Done. Two changes:
Committed as |
|
/oc amend the chore vs fix point to also include ci: but also make more concise |
|
Committed as |
|
/oc a bit better. Now amend prev commit in this pr to ensure all follow git conventions |
dac171a to
93d16c0
Compare
|
Done. Squashed 5 commits into one clean The old |
|
/oc why is base branch failing? Shouldn't it pass here? |
|
Committed. The base branch check was failing because |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📜 Recent review details
|
| Layer / File(s) | Summary |
|---|---|
PR validation permissions .github/workflows/check-base-branch.yml |
The validation job explicitly grants pull-requests: read permission while continuing to pass GITHUB_TOKEN to the validation step. |
Commit and PR conventions .opencode/skills/maintenance/SKILL.md, AGENTS.md |
Agent guidance requires CI-compatible Conventional Commits formatting for commits and PR titles, and reserves fix: for actual bug fixes rather than maintenance work. |
Estimated code review effort: 2 (Simple) | ~10 minutes
Possibly related PRs
- RussellSB/pytrendy#167: Updates contributor and agent documentation with overlapping Conventional Commits and PR title rules.
- RussellSB/pytrendy#244: Updates maintenance conventions and workflow permissions for agent-driven sessions.
- RussellSB/pytrendy#256: Expands
AGENTS.mdguidance around Conventional Commit formatting.
Suggested labels: documentation, automated
Suggested reviewers: russellsb
Poem
Tokens read, titles aligned,
Commit prefixes clearly signed.
Chores stay chores, fixes stay true,
CI knows what commits should do.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title is Conventional Commits-formatted and matches the main change: enforcing commit-format guidance in the maintenance skill. |
| Description check | ✅ Passed | The description is on-topic and matches the commit-format enforcement work tied to issue #267. |
| Linked Issues check | ✅ Passed | The PR adds stronger commit-format guidance before every commit and aligns PR-title rules, which satisfies #267's enforcement goal. |
| Out of Scope Changes check | ✅ Passed | The workflow permission tweak supports the branch-check changes and does not introduce unrelated scope. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✨ Finishing Touches
✨ Simplify code
- Create PR with simplified code
- Commit simplified code in branch
opencode/issue267-20260723060301
Warning
There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.
🔧 Checkov (3.3.8)
.github/workflows/check-base-branch.yml
Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.








Add one-liner at top of maintenance skill enforcing commit format verification before every
git commit. Impossible to miss during sessions.Closes #267