agentleFS
Sign inStart free
typvtypv/nest-turbo-starter/.claude/skills/git/SKILL.md

git

Skill224 starsChanged 3 months agoMITView on GitHub

Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If invoked without arguments, use AskUserQuestion to present available git operations:

    line 12
  2. Distinctive:

    Ensure token efficiency while maintaining high quality.

    line 28
  3. Very specific:

    If secrets found: STOP, warn user, suggest .gitignore.

    line 66
  4. Distinctive:

    Search for related issues on GitHub and add to body.

    line 71
  5. Very specific:

    Only use feat, fix, or perf prefixes for files in .claude directory (do not use docs).

    line 72

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

Default (No Arguments)

If invoked without arguments, use AskUserQuestion to present available git operations:

OperationDescription
cmStage files & create commits
cpStage files, create commits and push
prCreate Pull Request
mergeMerge branches

Present as options via AskUserQuestion with header "Git Operation", question "What would you like to do?".

Execute git workflows via git-manager subagent to isolate verbose output. Activate context-engineering skill.

IMPORTANT:

  • Sacrifice grammar for the sake of concision.
  • Ensure token efficiency while maintaining high quality.
  • Pass these rules to subagents.

Arguments

  • cm: Stage files & create commits
  • cp: Stage files, create commits and push
  • pr: Create Pull Request [to-branch] [from-branch]
    • to-branch: Target branch (default: main)
    • from-branch: Source branch (default: current branch)
  • merge: Merge [to-branch] [from-branch]
    • to-branch: Target branch (default: main)
    • from-branch: Source branch (default: current branch)

Quick Reference

TaskReference
Commitreferences/workflow-commit.md
Pushreferences/workflow-push.md
Pull Requestreferences/workflow-pr.md
Mergereferences/workflow-merge.md
Standardsreferences/commit-standards.md
Safetyreferences/safety-protocols.md
Branchesreferences/branch-management.md
GitHub CLIreferences/gh-cli-guide.md

Core Workflow

Step 1: Stage + Analyze

git add -A && git diff --cached --stat && git diff --cached --name-only

Step 2: Security Check

Scan for secrets before commit:

git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"

If secrets found: STOP, warn user, suggest .gitignore.

Step 3: Split Decision

NOTE:

  • Search for related issues on GitHub and add to body.
  • Only use feat, fix, or perf prefixes for files in .claude directory (do not use docs).

Split commits if:

  • Different types mixed (feat + fix, code + docs)
  • Multiple scopes (auth + payments)
  • Config/deps + code mixed
  • FILES > 10 unrelated

Single commit if:

  • Same type/scope, FILES ≤ 3, LINES ≤ 50

Step 4: Commit

git commit -m "type(scope): description"

Output Format

✓ staged: N files (+X/-Y lines)
✓ security: passed
✓ commit: HASH type(scope): description
✓ pushed: yes/no

Error Handling

ErrorAction
Secrets detectedBlock commit, show files
No changesExit cleanly
Push rejectedSuggest git pull --rebase
Merge conflictsSuggest manual resolution

References

  • references/workflow-commit.md - Commit workflow with split logic
  • references/workflow-push.md - Push workflow with error handling
  • references/workflow-pr.md - PR creation with remote diff analysis
  • references/workflow-merge.md - Branch merge workflow
  • references/commit-standards.md - Conventional commit format rules
  • references/safety-protocols.md - Secret detection, branch protection
  • references/branch-management.md - Naming, lifecycle, strategies
  • references/gh-cli-guide.md - GitHub CLI commands reference

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.

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