Skip to content

feat: accept Linear branch names in branch-validate skill - #19

Merged
skatz-alloy merged 1 commit into
masterfrom
feature/sig-263-align-branch-validate-skill-with-pre-push
Nov 16, 2026
Merged

skatz-alloy merged 1 commit into
masterfrom
feature/sig-263-align-branch-validate-skill-with-pre-push

Conversation

@skatz-alloy

Copy link
Copy Markdown
Contributor

ℹ️ Overview

  • branch-validate now accepts the Linear branch shape (type/issue-label) alongside the legacy type/TICKET/label
  • added the 100-character max branch length check
  • updated SKILL.md to prefer Linear's "Copy git branch name" and drop Jira-only wording
  • mirrors the same skill change in UseAlloy/Alloy#63314 (SIG-263)

🤖 Coding AI Authorship

  • Human-authored: written almost entirely by hand; maybe some autocomplete, sourced code or scaffolding.
  • Co-authored: agent wrote meaningful portions, significantly edited by me.
  • AI-authored: nearly all agent-authored with minimal human edits if any.

AI ported the Alloy PR's skill changes and tested the script locally.

🧪 Test Instructions

  1. skills/branch-validate/validate-branch.sh feature/ticket-123-example-branch-name exits 0
  2. skills/branch-validate/validate-branch.sh feature/TICKET-123/example-branch-name exits 0
  3. skills/branch-validate/validate-branch.sh task/bad exits 1 with the format help

Test Results

📝 Authoring Guidelines

Tip

Read through our full PR Guidelines.

As the author, I verify that I have:

  • Followed the test instructions and updated the test results.
  • Added/updated unit tests as applicable.
  • Added/updated documentation as applicable.

💬 Reviewer Guidelines

Tip

Read through our full PR Guidelines.

Reviewers are responsible for:

  • Reading the full PR description.
  • Evaluating all code changes, including edge cases and regressions.
  • Testing the change (locally or in ephemeral environments, if applicable).
  • Leaving thoughtful, actionable feedback.
  • Clearly signaling approval or requesting changes.

🚨 Risks

There may be possible side effects or negative impacts from these changes:

  • Authentication and/or authorization
  • Data privacy
  • Networking
  • Major configuration
  • Other core setup (please clarify below)

No significant risks - only loosens a skill's branch-name validation.

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@skatz-alloy
skatz-alloy marked this pull request as ready for review November 16, 2026 13:40
@skatz-alloy
skatz-alloy merged commit 3410e87 into master Nov 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants