agentleFS
Sign inStart free
SNIKOSNIKO/agent-skills/skills/git/SKILL.md

git

Skill2 starsChanged 6 months agoMITView on GitHub

Use when user asks for git operations: branch creation, committing changes, creating pull requests.

57 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • thechandanbhagatSkill

    sql

    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

  • 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

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

  • VercelSkill

    react

    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 AzureSkill

    test

    Also in 8 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 11

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    if branch not created, create branch first before committing or opening PR

    line 7
  2. Distinctive:

    if changes not committed, commit changes first before opening PR </constraints>

    line 8
  3. Distinctive:

    Check for the followings for repository specific rules and instructions related to git names/messages conventions and workflows:

    line 12
  4. Distinctive:

    Keep description under 72 characters

    line 39
  5. Distinctive:

    NEVER update git config

    line 40
  6. Very specific:

    NEVER run destructive commands (--force, hard reset) without explicit request

    line 41
  7. Very specific:

    NEVER skip hooks (--no-verify) unless user asks

    line 42
  8. Distinctive:

    NEVER force push unless the user explicitly requests it

    line 43
  9. Distinctive:

    NEVER commit to master/main unless repository rules allow it and the user confirms it

    line 44
  10. Distinctive:

    NEVER delete or rename existing branches without explicit user request

    line 51
  11. Distinctive:

    NEVER force-push or reset master/main

    line 52
  12. Distinctive:

    NEVER run destructive commands without confirmation

    line 53
  13. Distinctive:

    If branch already exists, report this to the user and ask how to proceed

    line 54

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<constraints> - if branch not created, create branch first before committing or opening PR - if changes not committed, commit changes first before opening PR </constraints>

<repository_rules> Check for the followings for repository specific rules and instructions related to git names/messages conventions and workflows:

  • AGETNS.md
  • CLAUDE.md
  • .agents/

Merge them with the general instructions below, with repository rules taking precedence in case of conflict. </repository_rules>

<workflows>

Commit

Commit message format:

<type>[scope]: <description>

<optional body>

<optional footer>

Rules

  • One logical change per commit, if many files changed, create multiple commits with clear scope and messages
  • Present tense: "add" not "added"
  • Imperative mood: "fix bug" not "fixes bug"
  • Reference issues: Closes #123, Refs #456
  • Keep description under 72 characters
  • NEVER update git config
  • NEVER run destructive commands (--force, hard reset) without explicit request
  • NEVER skip hooks (--no-verify) unless user asks
  • NEVER force push unless the user explicitly requests it
  • NEVER commit to master/main unless repository rules allow it and the user confirms it

Branch

Branch naming format: {type}/{semantic-name}

Rules

  • NEVER delete or rename existing branches without explicit user request
  • NEVER force-push or reset master/main
  • NEVER run destructive commands without confirmation
  • If branch already exists, report this to the user and ask how to proceed

Pull Request

Title format: {type}[scope]: {description}

Description format:

## Summary
{1–3 sentences explaining what this PR does and its scope}

## Changes
- {key change 1, do not repeat file changes, focus on observable behavior changes}
- {key change 2, do not repeat file changes, focus on observable behavior changes}
- {more as needed — keep each bullet atomic and concrete}

## Why
{motivation: what problem does this solve, or what goal does it achieve.}

## Breaking Changes
{describe what breaks and how consumers should migrate. Omit if no breaking changes.}

Git workflows for branching, committing, and opening pull requests, with automatic convention detection and branch-safety checks.

Types

Change types:

TypePurpose
featNew feature
fixBug fix
docsDocumentation only
styleFormatting/style (no logic)
refactorCode refactor
perfPerformance improvement
testAdd/update tests
buildBuild system/dependencies
ciCI/config changes
choreMaintenance/misc
</workflows>

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free