squad-pr-workflow

Enforce Git branch naming, PR formatting, and commit trailers.

1|Updated Jul 16, 2023

Search Tags:#git #workflow #code review #commit #branching #pr

Ready to run

npx skills add https://github.com/jmservera/aithena --skill squad-pr-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: squad-pr-workflow
Source: https://github.com/jmservera/aithena/tree/main/.squad/skills/squad-pr-workflow
Command: npx skills add https://github.com/jmservera/aithena --skill squad-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures consistent and standardized practices for Git branching, Pull Request (PR) creation, and commit messages within the squad, improving code review efficiency and maintainability.

Core Features & Use Cases

Standardized Branch Naming: Enforces a clear squad/{issue-number}-{kebab-case-slug} format.
Consistent PR Conventions: Mandates issue referencing, member mentions for labeled issues, and specific warning flags.
Commit Trailer Enforcement: Ensures the Co-authored-by: Copilot trailer is always included.
Stale PR Detection: Provides heuristics to identify and manage PRs that are no longer relevant.
Target Branch Enforcement: Directs all PRs to the dev branch for integration.

Quick Start

Ensure your new branch follows the 'squad/{issue-number}-{kebab-case-slug}' naming convention.

Frequently Asked Questions about squad-pr-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce standardized Git branch naming conventions for my team?▼

Pull requests are standardized by mandating issue referencing, member mentions for labeled issues, and specific warning flags. This ensures consistent PR formatting and improves code review efficiency within the squad.

How do I ensure the Co-authored-by Copilot trailer is included in Git commits?▼

Commit trailer enforcement ensures the `Co-authored-by: Copilot` trailer is always included in commit messages. This standardizes authorship attribution for squad agents working within the collaborative Git workflow.

What is the best way to detect stale Pull Requests in a Git repository?▼

Stale PR detection uses provided heuristics to identify and manage Pull Requests that are no longer relevant. This helps maintain repository hygiene and prevents outdated code reviews from blocking integration pipelines.

How do I direct all Pull Requests to a specific base branch for integration?▼

Target branch enforcement directs all Pull Requests to the `dev` branch for integration. This manages PR base branches automatically and adheres to Git best practices for structured collaborative development.

Does this Git workflow standardization require any specific dependencies or components?▼

No specific dependencies or components are required to use this Git workflow standardization. It operates independently to enforce branch naming, PR conventions, and commit trailers for squad agents without external tooling.