naming-convention-product

What problem does it solve?

This Skill enforces a consistent and understandable naming convention for code artifacts (branches, commits, PRs) that aligns with the product's core purpose and use cases, rather than internal processes.

Core Features & Use Cases

• Product Domain Mapping: Categorizes naming conventions under defined product domains (e.g., diagnosis, pipeline, API).
• Use Case Integration: Incorporates specific product use cases (e.g., API Latency, Database issues) into naming.
• Branch, Commit, and PR Naming: Provides clear formats and examples for naming branches, commit messages, and PR titles.
• Use Case: When creating a new branch for a feature that improves how the system diagnoses API latency issues, you would name it feature/diagnosis-api-latency instead of something process-oriented like feature/refactor-code-style.

Quick Start

Use the naming-convention-product skill to generate a product-centric name for a new feature branch related to the API batch endpoint.