skills.rest
tianjianjiang
tianjianjiangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

smith-style

Enforce file naming, path conventions, and commit patterns across repositories.

1|Updated Nov 25, 2025
Search Tags:#git#branching#commits#conventions#naming#path-standards
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smith-style
Source: https://github.com/tianjianjiang/smith/tree/main/smith-style
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

File naming, path standards, and conventional commits are often inconsistent across projects, leading to confusion, merge conflicts, and onboarding friction.

Core Features & Use Cases

  • Naming separators guidance: underscores for multi-word phrases and hyphens for variants or hierarchical relationships.
  • Path and file pattern guidance: examples for test files, config files, and docs to keep projects organized.
  • Commit and branch standards: prescribed formats and prefixes to improve traceability and review efficiency.

Quick Start

Apply these rules when starting a new project or updating an existing repository to ensure consistent naming, structured paths, and standardized commits.

Frequently Asked Questions about smith-style

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

FAQPage Schema
How do I enforce consistent file naming and path conventions across a git repository?▼

Conventional commits standardize commit messages using prescribed formats and prefixes to improve traceability and review efficiency across software engineering teams. This structured approach reduces confusion and onboarding friction when managing branch history.

When should I use underscores versus hyphens in file naming conventions?▼

Branch management standards prescribe specific formats and prefixes for branch naming to improve traceability and review efficiency. Implementing these conventions during PR creation ensures consistent commit patterns across your software engineering teams.

Can I apply these git commit and path standards to an existing repository?▼

Conventional commits standardize commit messages using prescribed formats and prefixes to improve traceability and review efficiency across software engineering teams. This structured approach reduces confusion and onboarding friction when managing branch history.

When should I use underscores versus hyphens in file naming conventions?▼

Branch management standards prescribe specific formats and prefixes for branch naming to improve traceability and review efficiency. Implementing these conventions during PR creation ensures consistent commit patterns across your software engineering teams.

Can I apply these git commit and path standards to an existing repository?▼

Inconsistent file naming and path standards create merge conflicts, confusion, and onboarding friction across repositories. Implementing conventional commits and structured branch management resolves these issues by enforcing consistent repository patterns.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
synaptiaisynaptiai
6

convention-enforcement

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

Official
Intermediate
TopengDevTopengDev

preflight

Run local linting, testing, and building checks before pushing code.

Community
Advanced
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced