git-workflow-architect

Generates Git workflow configurations including commitlint, husky hooks, PR templates, and CI pipelines.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/Scardubu/SwarmXQ --skill git-workflow-architect-scardubu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow-architect
Source: https://github.com/Scardubu/SwarmXQ/tree/main/.ai/skills/git-workflow-architect
Command: npx skills add https://github.com/Scardubu/SwarmXQ --skill git-workflow-architect-scardubu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a consistent Git workflow involves many interdependent pieces—commit message linting, pre-commit hooks, PR templates, CI pipelines, and semantic release—that are easy to misconfigure or set up in the wrong order. This Skill generates complete, copyable configuration files for the entire stack so nothing is missed. ## Core Features & Use Cases - Conventional Commits Tooling: Generates commitlint config, commitizen setup, husky hooks, and lint-staged configuration with correct dependency ordering. - CI/CD Pipelines: Produces GitHub Actions workflows for validation, build, commit linting, and optional semantic-release automation. - Branch Strategy Guidance: Provides trunk-based and Gitflow branch models with concrete recommendations. - Use Case: A developer starting a new Next.js monorepo asks to set up conventional commits and CI; the Skill outputs commitlint.config.ts, .husky hooks, a PR template, and a ci.yml workflow ready to commit. ## Quick Start Ask the assistant to set up conventional commits with husky, commitlint, and a GitHub Actions CI workflow for your Node.js project.

Frequently Asked Questions about git-workflow-architect

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

FAQPage Schema
How do I set up conventional commits with commitlint and husky?

Install @commitlint/cli, @commitlint/config-conventional, commitizen, cz-conventional-changelog, husky, and lint-staged as dev dependencies, then run husky init. Add a commit-msg hook running commitlint and a pre-commit hook running lint-staged, plus a commitlint.config.ts extending the conventional config.

What branch strategy should I use for my team?

Trunk-based development is recommended for teams shipping fast: a main branch that is always deployable with short-lived feature and fix branches merged via PR. Gitflow suits scheduled releases, using develop, feature, hotfix, and release branches.

How do I set up semantic release with GitHub Actions?

Install semantic-release with the changelog, git, and github plugins, then configure .releaserc.json with your branches and plugins. Add a release job to CI that runs only on pushes to main, using GITHUB_TOKEN and NPM_TOKEN secrets.

Does this Git workflow setup work with pnpm monorepos?

Yes, the generated configurations use pnpm throughout, including pnpm install --frozen-lockfile in CI and pnpm turbo build for Turborepo monorepos. The husky hooks and lint-staged config work at the repository root regardless of workspace structure.

Why is my commit rejected by commitlint?

Commitlint rejects messages that do not follow the conventional commit format, such as missing type prefixes like feat or fix, uppercase subjects, or subjects over 100 characters. Run git commit interactively through commitizen with pnpm commit to get a guided prompt that produces valid messages.