skills.rest
wednesday-solutions
wednesday-solutionsOFFICIAL
Explore all skills by this author →
Website𝕏@wednesdaysolGitHub

wednesday-git

Standardize Git sprint branching, atomic commits, and PR creation with commitlint checks.

165|20|Updated Feb 2, 2026
Search Tags:#git#pull request#conventional commits#commitlint#branching#github cli#CI quality gates
One-click install
npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill wednesday-git
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wednesday-git
Source: https://github.com/wednesday-solutions/ai-agent-skills/tree/main/skills/wednesday-git
Command: npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill wednesday-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents AI and developers from making repository-breaking mistakes by standardizing branch naming, commit structure, and PR hygiene so changes are reviewable and predictable.

Core Features & Use Cases

  • Sprint branching that follows strict conventions: Creates feature branches using the type/name format with kebab-case and a 40-character limit to keep history organized and searchable.
  • Atomic commit workflow with enforceable quality: Ensures conventional commit messages, one logical change per commit, and commitlint validation so PRs remain coherent and standards-compliant.
  • PR creation with a safety and quality checklist: Enforces lint/test/build pre-push gates, validates title and description structure, limits PR size (max 6 files), and optionally blocks risky pushes based on risk scoring thresholds.

Quick Start

Open a feature ticket and ask the AI to run the Wednesday Git workflow by creating a sprint branch, producing atomic conventional commits that pass commitlint, and then opening a PR using the required checklist and PR description template.

Frequently Asked Questions about wednesday-git

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

FAQPage Schema
How do I enforce conventional commits and commitlint checks before pushing a Git branch?▼

You can enforce conventional commits and commitlint checks by applying pre-push validation commands that reject non-compliant messages. This standardizes atomic commit workflows, ensuring each commit represents one logical change and passes linting before integration.

What's the best way to standardize Git branch naming for feature development and bugfixes?▼

Standardize Git branch naming by enforcing a type/name format using kebab-case with a strict character limit. This keeps repository history organized and searchable, preventing naming collisions and ensuring predictable branch tracking across sprints.

How do I automate pull request creation with quality gates using GitHub CLI?▼

Automate pull request creation using GitHub CLI operations to validate PR titles, enforce description templates, and apply risk scoring thresholds. Pre-push commands run lint, test, and build gates to block risky pushes before PR submission.

Can I limit pull request size to reduce integration failures and review churn?▼

Yes, you can limit pull request size by enforcing a maximum file count per PR. Restricting PRs to a set number of files enforces atomic commits, reduces integration failures, and minimizes review churn.

Why should I use pre-push commands for CI quality gates in my Git workflow?▼

Pre-push commands act as CI quality gates by running lint, test, and build validations locally before code reaches the repository. This prevents repository-breaking mistakes, ensuring changes are reviewable and predictable.

Does this Git workflow support branch naming rules and PR templates for sprint branching?▼

Yes, this workflow applies branch naming rules and PR description templates specifically for sprint branching. It standardizes the end-to-end Git process from feature branch creation through PR delivery.

Related Skills

Explore More Software Engineering Skills→
garochee33garochee33
3

github

Manage GitHub repository operations including pull request triage, Actions monitoring, branch protection, and releases.

Community
Advanced
agentic-inagentic-in
577

GitHub PR Workflow

Prepare, review, and merge GitHub pull requests with validation.

Official
Intermediate
redpanda-dataredpanda-data
34

setup-quality-gate

Set up a quality gate with biome, tsgo, and vitest.

Official
Advanced
shellicarshellicar

flightrac-conventions

Enforce Git and PR conventions for Flightrac projects on Azure DevOps.

Community
Basic