agentleFS
Sign inStart free
maragudkmaragudk/skills/git/SKILL.md

git

Skill49 starsChanged 9 months agoMITView on GitHub

Guide for using git according to my preferences. Use it when you're asked to commit something.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always enclose code identifiers with backticks.

    line 17
  2. Very specific:

    Always refer to Go code identifiers including the package name, like in html.UserPage above.

    line 18
  3. Distinctive:

    Don't mention that you've updated tests, that's assumed.

    line 20
  4. Distinctive:

    Don't amend previous commits unless instructed to.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 46 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

git

Most of git usage is what you already know, so depend on that. This is skill is just a refinement.

Branch naming

Just name the branch a short sentence seperated with dashes. Example: add-some-feature. Don't use feat/, hotfix/ etc. prefixes.

Commit messages

  • Always enclose code identifiers with backticks. Example: "Add html.UserPage component"
  • Always refer to Go code identifiers including the package name, like in html.UserPage above. Fields and methods on structs can be referred with model.User.Name.
  • Ask me about any Github issues that should be referenced. Reference them at the end of the commit message like this: "See #123, #234". If the commit fixes one or more issues, use "Fixes #123, fixes #234" instead (the double "fixes" is important for Github to actually close the issue).
  • Don't mention that you've updated tests, that's assumed.

Committing

  • Don't amend previous commits unless instructed to. When committing after the first commit on a branch, just commit with a simple message (e.g. "fixing …"), because the branch will most times be squashed on Github anyway.

Download now (ZIP)

  • Other versions51 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 51

    1. macro-inc/macro★ 6ksame name
    2. epicenter-md/epicenter★ 4.8ksame name
    3. EpicenterHQ/epicenter★ 4.8ksame name
    4. carapace-sh/carapace-bin★ 2ksame name
    5. LuisaGroup/LuisaCompute★ 1.1ksame name
    6. kagenti/kagenti★ 300same name
    7. Conceptual-Machines/magda-core★ 248same name
    8. typv/nest-turbo-starter★ 224same name
    9. matteing/opal★ 59same name
    10. tsukhani/jclaw★ 41same name

    41 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.

  • Used alongsideProjects with it also use databases, devops and 9 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.
    • mrgoonieSkill

      databases

      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

    • Microsoft AzureSkill

      test

      Also in 7 projects that use this

    • AnthropicSkill

      debug

      Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

      Also in 8 projects that use this

    • Microsoft AzureSkill

      design

      Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

      Also in 7 projects that use this

    • MicrosoftSkill

      typescript

      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 3 projects that use this

    • +1 more from Azure
  • In this repository20 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free