skills.rest
synaptiai
synaptiaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

convention-enforcement

Validate git history and pull requests against repository-specific conventions.

6|2|Updated Dec 19, 2025
Search Tags:#git#commit messages#validation#pull requests#conventions#branch naming
One-click install
npx skills add https://github.com/synaptiai/synapti-marketplace --skill convention-enforcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convention-enforcement
Source: https://github.com/synaptiai/synapti-marketplace/tree/main/plugins/flow/skills/convention-enforcement
Command: npx skills add https://github.com/synaptiai/synapti-marketplace --skill convention-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces repository-specific git conventions to prevent defective commits, inconsistent branch names, and improperly formatted pull requests that impede collaboration, traceability, and automated workflows.

Core Features & Use Cases

  • Commit message validation: Checks type, optional scope, subject length, and matches configured commit types and subject length limits.
  • Branch naming validation: Verifies current branch patterns against configured branchPatterns and warns on direct commits to the default branch.
  • PR format and issue linkage checks: Ensures PR titles follow conventional commit style, PR bodies include summary and linked issues, labels are present, and draft status is appropriate.
  • Project-specific detection and adaptation: Infers conventions from CLAUDE.md, settings.flow.json, recent commits, and existing branches to adapt validation rules.
  • Use Case: Run before PR creation or during code review to catch non-conforming commits, missing issue links, and PR formatting errors and provide actionable fixes.

Quick Start

Run a repository convention check that validates commit messages, branch naming, PR format, and issue linkage and then list all violations with severity and suggested fixes.

Frequently Asked Questions about convention-enforcement

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

FAQPage Schema
How do I enforce git commit message conventions before a pull request?▼

To enforce git commit message conventions before a pull request, validate commit types, scopes, and subject lengths against configured limits. This process flags non-conforming commits and produces a severity-ranked report with actionable remediation suggestions.

How do I validate branch naming patterns in a GitHub repository?▼

Validating branch naming patterns involves comparing current branch names against configured branchPatterns. This workflow warns on direct commits to the default branch and detects inconsistencies to maintain repository structure and traceability.

Can I check pull request formatting and issue linkage automatically?▼

Yes, you can check pull request formatting and issue linkage automatically. Validation ensures PR titles follow conventional commit style, verifies PR bodies include summaries and linked issues, and checks that labels and draft statuses are appropriate.

How do I configure custom git conventions for an existing project?▼

You can configure custom git conventions by defining rules in CLAUDE.md or settings.flow.json overrides. The validation system infers and adapts to project-specific commit types and branch patterns from these files and recent repository history.

What is the best way to catch missing issue links during code review?▼

The best way to catch missing issue links during code review is to run automated validation during PR creation. It detects missing issue linkage in PR bodies, flags the omission by severity, and provides suggested fixes to ensure traceability.

Why should I validate PR titles against conventional commit styles?▼

Validating PR titles against conventional commit styles prevents improperly formatted pull requests that impede collaboration and automated workflows. It ensures titles match configured commit types and subject limits, generating a report to fix violations.

Related Skills

Explore More Software Engineering Skills→
kang8kang8
2

commit

Create git commits from staged changes with branch naming and validation.

Community
Advanced
guhans6guhans6

caveman-review

Generate code review comments with severity levels for pull requests.

Community
Basic
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
u9401066u9401066

git-pusher

Automate Git commit, push, and CI workflow triggering with pre-push validation.

Community
Intermediate