What merge strategy is recommended by this skill?

It prioritizes regular merge commits over squashing or rebasing to preserve the individual atomic history of how the code evolved.

Why does it use the GitHub CLI for mentions?

To prevent tagging the wrong person, the skill uses the GitHub CLI to programmatically verify the author of issues or PRs before adding @mentions to comments.

Does this skill add AI attribution to my commits?

No, this skill is specifically designed to never include 'Generated with Claude' watermarks or AI attribution in your commit messages or PR descriptions.

What commit message format does this skill support?

It follows the Conventional Commits specification, using types like feat, fix, docs, and refactor, with support for optional scopes and breaking change indicators.

How does it handle pull request descriptions?

It generates clean, narrative paragraphs focusing on technical decisions and user benefits, avoiding redundant file lists and corporate marketing language.

Conventional Git & PR Workflow

Name: Conventional Git & PR Workflow
Author: EpicenterHQ

byEpicenterHQ

•

3,817

Developer Tools

Enforces professional Git commit standards and narrative-style pull request descriptions following the Conventional Commits specification.

About

This skill optimizes the development lifecycle by standardizing how Git commits and pull requests are structured. It enforces the Conventional Commits format—integrating types like feat, fix, and breaking changes—to ensure project histories are readable and compatible with semantic versioning. Beyond commits, it guides the creation of narrative PR descriptions that focus on the 'why' behind changes rather than just the 'what,' while explicitly stripping out AI watermarks and providing programmatic safeguards for GitHub mentions and merge strategies.

Key Features

Prevents AI-generated watermarks or Claude Code attribution
Mandates merge commit strategies to preserve development history
Enforces Conventional Commits standards (feat, fix, refactor, etc.)
Integrates GitHub CLI for precise @username verification
Generates narrative-style PR descriptions without bulleted lists
3,817 GitHub stars

Use Cases

Standardizing commit history for professional open-source repositories
Automating high-quality PR descriptions for team-based code reviews
Ensuring semantic versioning accuracy through structured commit types

About

Key Features

Prevents AI-generated watermarks or Claude Code attribution
Mandates merge commit strategies to preserve development history
Enforces Conventional Commits standards (feat, fix, refactor, etc.)
Integrates GitHub CLI for precise @username verification
Generates narrative-style PR descriptions without bulleted lists
3,817 GitHub stars

Use Cases

Standardizing commit history for professional open-source repositories
Automating high-quality PR descriptions for team-based code reviews
Ensuring semantic versioning accuracy through structured commit types