repo-conventions

Solid

Conventions for working in this repository — commit style, branch naming, and testing expectations. Use when writing commits, opening PRs, or adding tests here.

Code & Development 2,482 stars 282 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Repo conventions Search the bundled docs before guessing: ``` bb docs search "conventional commits" ``` - Commits follow conventional-commit style (`feat(scope): summary`). - Branches are named `bb/<topic>`. - Every bug fix ships with a regression test.

Details

Author: get-bb
Repository: get-bb/bb
Created: 5 months ago
Last Updated: today
Language: TypeScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

github-conventions

GitHub conventions -- branch naming, commit format, issue/PR templates, and safe issue/PR referencing in comments.

2 Updated 2 days ago

Jartan-LLC

Code & Development Listed

git-conventions

Branch naming, commit message format, PR workflow, worktree conventions, versioning policy

1 Updated today

sefaertunc

Code & Development Listed

git-conventions

Use before writing any commit message, creating a branch, opening a pull request, or splitting work into commits. Enforces Conventional Commits (type, optional scope, imperative description, body, footers, breaking-change markers) and the type/ticket-description branch naming pattern. Also carries the house rules that a commit is never made without asking first and never carries a Claude co-author trailer.

0 Updated 2 weeks ago

localhostd3veloper