agentleFS
Sign inStart free
weselbenweselben/RooForge/skills/use-git-identity/SKILL.md

use-git-identity

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Set the git identity (name + email) before any commit, amend, or rebase. Apply repo-local on first commit; use `-c` for one-offs.

  • Deletes or force-pushes
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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
  1. Distinctive:

    Every commit on this machine uses one identity — author AND committer:

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Use Git Identity

Note: the defaults below are the maintainer's identity. forge-setup step 6 prompts the user on first install and rewrites these values with the user's own user.name and user.email before any commit lands. Until that runs, commits carry the maintainer's identity.

Every commit on this machine uses one identity — author AND committer:

name:  weselben/rooforge
email: bengottwaldi04@gmail.com

Apply

First commit in a repo — set repo-local (never --global unless asked):

git config user.name "weselben/rooforge"
git config user.email "bengottwaldi04@gmail.com"

One-off (no config touch):

git -c user.name="weselben/rooforge" -c user.email="bengottwaldi04@gmail.com" commit ...

Fix authorship of an existing commit:

git config user.name "weselben/rooforge"
git config user.email "bengottwaldi04@gmail.com"
git commit --amend --reset-author --no-edit

Rewrite pushed history: git push --force-with-lease — confirm with user first unless they asked for the force push.

Boundaries

  • Set user.name and user.email before every commit. A failed git commit from a missing identity means this skill was skipped.
  • Force-pushes that rewrite history require explicit user confirmation.

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