astrobyte-git-identity
Skill1 starsChanged 14 days agoMITView on GitHub
Attribute Git commits made by an agent to both the operator and the active agent product without changing the operator's normal Git identity. Use before an agent creates, amends, or pushes commits.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/adopt-skill-stack.mdcCursor rule
- adopt-skill-stackSkill
- api-and-interface-designSkill
- astrobyte-architectSkill
- astrobyte-modeSkill
- astrobyte-project-startupSkill
- astrobyte-pr-workflowsSkill
- astrobyte-recallSkill
- astrobyte-reviewSkill
- astrobyte-show-workSkill
- astrobyte-tddSkill
- astrobyte-verify-projectSkill
- blast-radiusSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- codebase-designSkill
- continual-improvement-checkSkill
- deprecation-and-migrationSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- grillingSkill
- handoffSkill
- hermetic-test-suitesSkill
- observability-and-instrumentationSkill
- performance-optimizationSkill
- pr-feedback-loopSkill
- prototypeSkill
- researchSkill
- security-and-hardeningSkill
- setup-astrobyte-skillsSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- technical-writingSkill
- to-questionnaireSkill
- typescript-best-practicesSkill
- unslopSkill
- update-skill-stackSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 16
Use this skill's scripts/git_agent_identity.py for every agent-created commit.
- Very specific: line 34
When git_identity.verify_before_push is true, audit the unpublished range before pushing:
≈ “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.
Files
Astrobyte Git identity
Read machine config from ${ASTROBYTE_CONFIG} when set, otherwise ~/.config/astrobyte-agent-skills/config.json. When the optional file is absent, use this skill's packaged Git policy. Resolve the active agent product before committing. The helper uses the explicit configured human identity when present, otherwise the current environment's Git author variables and effective Git configuration, including conditional includes. Missing local configuration does not require installation or onboarding.
When author identity is unresolved, ask only for the colleague's own Git name and email when a commit requires them. An explicitly selected missing or malformed config is an error to resolve. If an explicit policy disables attribution, report that choice and use ordinary Git only within the user's authorization; the helper refuses attributed commits in disabled mode.
When attribution is enabled, a helper failure blocks the commit and push. Run the installed helper and inspect its actual error before reporting a blocker. Missing optional machine config is supported; do not prescribe setup to create it. A failure on that missing file may indicate an outdated or incomplete installed package. Report the error and required refresh directly to the operator. Do not silently fall back to an unattributed commit or add setup diagnostics to an unrelated PR description.
Commit
Use this skill's scripts/git_agent_identity.py for every agent-created commit. Pass the active product explicitly:
python3 <skill-directory>/scripts/git_agent_identity.py --harness codex commit -- -m "feat: describe the change"In the recommended dual-attribution mode, the helper records:
- the operator as author;
- the active agent product as committer;
- an
Agent: <name> <email>commit trailer.
The helper applies identity to one command. It does not write global, repository, or worktree Git configuration. A later human commit therefore uses the operator's normal Git identity and has no agent trailer.
For an amend, preserve the existing author unless the operator approves a change in authorship. The helper supplies the agent committer and trailer, and records the preserved author in an Agent-Original-Author trailer. Later audits require that matching preservation record when the author differs from the current identity. New commits still verify against the configured author. Do not rewrite a published commit only to fix attribution without explicit approval.
Push
When git_identity.verify_before_push is true, audit the unpublished range before pushing:
python3 <skill-directory>/scripts/git_agent_identity.py --harness codex auditInspect every agent, human, and invalid line. Stop if an agent-created commit is attributed as human-only, uses the wrong product identity, or lacks the configured trailer. Resolve an unknown upstream range explicitly. If verification is disabled, state that the configured audit was skipped.
A push does not change commit identity. GitHub still records the authenticated account or GitHub App as the push and pull-request actor. A distinct remote actor requires separate bot or App credentials and separate approval.
The identity check is complete when the unpublished commits show the intended author, committer, and trailer, and ordinary Git configuration remains unchanged.
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.

