Skip to content

Update conventional-branch skill to Conventional Branch 1.1.0 - #5131

Open
shenxianpeng wants to merge 1 commit into
github:mainfrom
shenxianpeng:chore/update-conventional-branch-skill
Open

shenxianpeng wants to merge 1 commit into
github:mainfrom
shenxianpeng:chore/update-conventional-branch-skill

Conversation

@shenxianpeng

Copy link
Copy Markdown
Contributor

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services. (Not applicable: the skill involves no paid services.)
  • My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot. (Not re-tested in Copilot for this update; the change is to the skill's reference content only, and the workflow steps are unchanged.)
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the main branch for this pull request.

Description

This updates the conventional-branch skill, added in #1858, to match the current Conventional Branch specification (1.1.0). The existing text predates that release:

  • AI agent source prefixes: adds ai/, copilot/, cursor/, claude/ and codex/, which 1.1.0 made valid types, with examples. Without them, the skill tells Copilot that its own copilot/… branches are invalid.
  • Dots: the skill said dots are allowed only in release/ descriptions. The spec's grammar has always accepted them in any description (chore/upgrade-node-v20.11), and its text now says so.
  • Link: the spec moved from conventional-branch.github.io to conventionalbranch.org, and the link is updated to the new domain.
  • Validation: adds a short section pointing to commit-check / commit-check-action and the spec's enforcement page.

The description in the front matter now lists the AI prefixes too. docs/README.skills.md was regenerated with npm run build, and npm run skill:validate passes.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • New canvas extension.
  • Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
  • Other (please specify):

Additional Notes

I maintain the Conventional Branch specification and contributed this skill originally. The specification's own copy of the skill is at conventional-branch/conventional-branch.


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Add the AI agent source prefixes (ai/, copilot/, cursor/, claude/, codex/), allow dots in any description as the grammar does, link the spec's current domain, and point to commit-check for validation. Regenerate docs/README.skills.md.
@shenxianpeng
shenxianpeng requested review from a team as code owners October 16, 2026 22:43
@github-actions github-actions Bot added the skills PR touches skills label Oct 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔒 PR Risk Scan Results

Scanned 1 changed file(s).

Severity Count
🔴 High 0
🟠 Medium 0
ℹ️ Info 0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

@github-actions

Copy link
Copy Markdown
Contributor

🔴 Contributor Reputation Check: HIGH risk

Check Risk
Profile HIGH
Credential audit NONE

Maintainers: please review this contributor before merging.
See the workflow run for full details.
Automated check powered by AGT.

@github-actions

github-actions Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier
  • Label needs-review:HIGH flags a high contributor-risk signal

Automated checks

Check Status Details
Line endings ✅ Passed Passed · logs
Spelling ✅ Passed Passed · logs
Generated README consistency ✅ Passed Passed · logs
Skill validation ✅ Passed Passed · logs
Skill lint (vally) ✅ Passed Passed · logs
Risk scan ✅ Passed Passed · logs
Contributor reputation ✅ Passed Passed · logs
Duplicate resource scan ✅ Passed Passed · logs
PR quality signal ⏭️ Skipped Skipped by its workflow · logs

Review

  • Approvals: 0/1
  • Assigned reviewer: not assigned yet — comment /request-review to ask for one
  • Review target date: not set
  • Still needed: 1 more approval(s); an approval from a maintainer with admin or maintain permission
  • The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command Who What it does
/rerun-checks PR author, maintainers Re-runs failed or incomplete checks and re-evaluates this gate
/request-review PR author, maintainers Asks the review rotation to assign a reviewer (adds needs-reviewer)

Updated for 0355990 · gate run · This comment is maintained automatically — see submission gate docs.

@github-actions github-actions Bot added the needs-review:HIGH Contributor reputation check flagged HIGH risk label Oct 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔍 Vally Lint Results

✅ All checks passed

Scope Checked
Skills 1
Agents 0
Total 1
Severity Count
❌ Errors 0
⚠️ Warnings 0
ℹ️ Advisories 0

Summary

Level Finding
ℹ️ ✅ conventional-branch (2/2 checks passed)
ℹ️ ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️ ✓ spec-compliance: All spec checks passed.
ℹ️ ✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️ ✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️ 1 skill(s) linted, 1 passed
Full linter output
### Linting skills/conventional-branch
✅ conventional-branch (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

@github-actions github-actions Bot added ready-for-review Submission passed intake validation and is ready for maintainer review and removed awaiting-automation labels Oct 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-risk:high needs-review:HIGH Contributor reputation check flagged HIGH risk ready-for-review Submission passed intake validation and is ready for maintainer review skills PR touches skills

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant