skills.rest
martimramos
martimramosCOMMUNITY
Explore all skills by this author →
GitHub

forge-conventions

Standardizes git commits, branch names, and code style via configurable rules.

1|Updated Dec 20, 2025
Search Tags:#workflow#linting#code-style#branch-naming#git-commit#review-guidelines#forge-conventions
One-click install
npx skills add https://github.com/martimramos/claude-forge --skill forge-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-conventions
Source: https://github.com/martimramos/claude-forge/tree/main/skills/conventions
Command: npx skills add https://github.com/martimramos/claude-forge --skill forge-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes git commits, branch names, and code style across a repository.

Core Features & Use Cases

  • Git Commit Style: Enforces a consistent commit message format (e.g., Conventional Commits) across all contributions.
  • Branch Naming: Applies a standardized prefix scheme (feature/, fix/, docs/, etc.) to branches.
  • Code Style: Provides a shared code-style guide and linting expectations to improve readability and maintainability.
  • Review Guidelines: Establishes guidelines for code reviews and merge checks to streamline collaboration.
  • Use Case: When coordinating a multi-person project, teams align on messages, prefixes, and style to reduce review time.

Quick Start

Adopt forge-conventions to standardize commits, branches, and style across your project and configure CI or pre-commit hooks to enforce the rules.

Frequently Asked Questions about forge-conventions

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

FAQPage Schema
How do I standardize git commit messages and branch naming conventions across a development team?▼

Standardize git commit messages and branch naming conventions by applying a centralized reference guide for Conventional Commits and branch prefixes like feature/ or fix/. This unifies team contributions and streamlines code reviews.

What is the best way to enforce code style and linting expectations in a collaborative repository?▼

The best way to enforce code style and linting expectations is to configure CI pipelines or pre-commit hooks using centralized linting templates. This automates governance and improves code readability and maintainability across the repository.

Can I use centralized review guidelines to streamline merge checks for multi-person projects?▼

Yes, you can use centralized review guidelines to streamline merge checks for multi-person projects. Establishing specific code review practices reduces review time and ensures team alignment on style and commit formats.

Does this convention system support pre-commit hooks for automated governance?▼

Yes, the system supports pre-commit hooks for automated governance. It provides CI and linting templates that you can configure to automatically enforce commit styles, branch prefixes, and code review rules before changes are merged.

When do I need to implement frontmatter-based SKILL.md definitions for repository conventions?▼

You need to implement frontmatter-based SKILL.md definitions when setting up centralized repository conventions. This approach provides a structured reference guide that standardizes git commits, branch names, and code style across teams.

Related Skills

Explore More Software Engineering Skills→
InfantLabInfantLab
4

god-mode

Summarize repository status and coach AGENTS.md instructions across GitHub and Azure DevOps.

Community
Advanced
0xjc65eth0xjc65eth
4

git-ops

Standardize Git commits, branching, pre-merge checks, and deployments for CYPHER V3.

Community
Intermediate
richardnguyen0715richardnguyen0715

requesting-code-review

Automate pre-commit code review with security scans, quality checks, and auto-fixes.

Community
Advanced
ianyimiianyimi
1

Global Coding Style

Enforce global coding style guidelines across multi-language codebases.

Community
Basic