git
Skill59 starsChanged 9 months agoMITView on GitHub
Enforces conventional commit messages and good git hygiene. Use this skill automatically whenever creating commits, preparing PRs, or performing any git operations in this repository.
57 other projects use a version of this.
Adopted by
Most recently taken up by
- bmcszk/agent-skillstheir own version, first seen Nov 8, 2026
- BridgLabs/opencodereviewtheir own version, first seen Nov 8, 2026
- Conceptual-Machines/magda-coretheir own version, first seen Nov 7, 2026
- tsukhani/jclawtheir own version, first seen Nov 5, 2026
- cekrauseee/harnesstheir own version, first seen Nov 1, 2026
- jmlrt/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use sql, databases and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
thechandanbhagatSkillsql
Write SQL queries, optimize database performance, design schemas, and debug SQL issues. Use for database operations, query optimization, and schema design.
Also in 4 projects that use this
mrgoonieSkilldatabases
Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.
Also in 3 projects that use this
- mrgoonieSkill
devops
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.
Also in 4 projects that use this
MicrosoftSkilltypescript
TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.
Also in 4 projects that use this
VercelSkillreact
React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.
Also in 3 projects that use this
Microsoft AzureSkilltest
Also in 8 projects that use this
Other versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 57
- macro-inc/macro★ 6ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- carapace-sh/carapace-bin★ 2ksame name
- LuisaGroup/LuisaCompute★ 1.1ksame name
- kagenti/kagenti★ 303same name
- Conceptual-Machines/magda-core★ 258same name
- typv/nest-turbo-starter★ 224same name
- BridgLabs/opencodereview★ 79same name
- maragudk/skills★ 49same name
47 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ci-preflightSkill
- citationsSkill
- codegen-syncSkill
- debuggingSkill
- docsSkill
- elixir-cyclic-depsSkill
- lint-and-formatSkill
- live-testsSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Every commit message MUST follow this format:
- Distinctive: line 40
Use a scope to identify the affected area:
- Distinctive: line 68
Always: use conventional commit format.
- Distinctive: line 69
Description: must be lowercase, imperative mood, no period at the end.
- Distinctive: line 70
Scope: should match the table above when the change is localized.
- Distinctive: line 72
One logical change per commit: Don't bundle unrelated changes.
- Distinctive: line 73
Before committing, verify the message parses as a valid conventional commit.
“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Git Conventional Commit Skill
You enforce Conventional Commits on every commit in this repository. This is critical for consistent changelogs and semantic version bumps.
Commit message format
Every commit message MUST follow this format:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]Types (required)
| Type | When to use | Version bump |
feat | A new feature or capability | minor |
fix | A bug fix | patch |
docs | Documentation only | none |
style | Formatting, semicolons, whitespace — no logic | none |
refactor | Code change that neither fixes a bug nor adds a feature | none |
perf | Performance improvement | patch |
test | Adding or correcting tests | none |
build | Build system or external dependency changes | none |
ci | CI configuration changes | none |
chore | Maintenance tasks (deps, tooling, releases) | none |
Scopes (recommended)
Use a scope to identify the affected area:
| Scope | Meaning |
core | Elixir core (lib/opal/ directory) |
cli | TypeScript CLI (cli/ directory) |
rpc | JSON-RPC protocol layer |
agent | Agent loop / GenServer |
tools | Built-in tool implementations |
ci | GitHub Actions workflows |
release | Release and versioning infrastructure |
docs | Documentation |
sdk | TypeScript SDK client |
Omit the scope only when the change truly spans the entire project.
Breaking changes
Append ! after the type/scope for breaking changes:
feat(rpc)!: change message envelope formatOr add a BREAKING CHANGE: footer in the body.
Rules
- Always use conventional commit format. Never commit with a bare message like "fix stuff" or "updates".
- Description must be lowercase, imperative mood, no period at the end.
- Scope should match the table above when the change is localized.
- Body is optional but encouraged for non-trivial changes — explain why, not what.
- One logical change per commit. Don't bundle unrelated changes.
- Before committing, verify the message parses as a valid conventional commit.
Examples
feat(cli): add --json flag for machine-readable output
fix(core): prevent crash when tool returns empty response
docs(tools): document edit tool hashline format
refactor(agent): extract token counting into dedicated module
ci: add Elixir dialyzer step to CI pipeline
chore(release): 0.1.10
feat(rpc)!: switch from JSON-RPC 2.0 to msgpack framing
BREAKING CHANGE: RPC wire format changed from JSON to msgpack.
Clients must update to sdk >= 0.2.0.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.