shellicar-oss-conventions

Standard git commit message conventions for npm packages enforce a structured pattern for commits, reducing repository drift and miscommunication across GitHub repositories. They ensure clear PR workflows, issue linking, and co-authorship attribution.

To format branch naming for feature work and fixes, apply standardized guidelines that reflect the specific work type. This ensures branches align with milestones and PR workflows across the repository's development cycle.

A PR description for GitHub repositories should include a descriptive title, a structured body, issue linking, milestone linking, and co-authorship practices. This standardizes the PR workflow and ensures proper author attribution.

Yes, you need YAML frontmatter in SKILL.md for git conventions to ensure it includes a required name and description. This encodes the standardized metadata and supports optional scripts, references, and assets.

Yes, you can use these PR workflows across multiple GitHub repositories. The conventions apply broadly to standardize branch naming, commit messages, and milestone linking, reducing miscommunication and repository drift.

Use standardized git and PR conventions for npm packages to reduce miscommunication and repository drift. Consistent branch naming, commit messages, and PR workflows ensure clear author attribution and structured development.