attribution

Remove bot co-author trailers and tool footers from AI-generated git commits.

89|17|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/statsclaw/statsclaw --skill attribution-statsclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: attribution
Source: https://github.com/statsclaw/statsclaw/tree/main/skills/attribution
Command: npx skills add https://github.com/statsclaw/statsclaw --skill attribution-statsclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the problem of AI-generated commits incorrectly attributing work to bots or tooling, which pollutes repository contributor graphs, leaks session identifiers, and violates user authorship rights.

Core Features & Use Cases

  • Strict Attribution Policy: Blocks all bot co-author trailers, tool footers, session URLs, and bot identity configuration from commit messages.
  • Cross-Agent Enforcement: Applies to commits from all StatsClaw pipeline agents across target repos, workspace repos, and brain-seedbank forks.
  • Use Case: For development teams using AI-assisted workflows, this ensures commit history accurately reflects only human contributors, keeping audit trails clean and contributor graphs meaningful.

Quick Start

Use the attribution skill to configure all StatsClaw agents to never add bot attribution or co-author trailers to any commit messages they create.

Frequently Asked Questions about attribution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove bot co-author trailers from AI-generated git commit messages?

To remove bot co-author trailers from AI-generated git commit messages, you need an attribution policy that blocks bot co-author trailers, tool footers, and session URLs. This enforces strict user-only authorship, keeping contributor graphs clean.

Why does AI tooling attribution pollute repository contributor graphs?

AI tooling attribution pollutes repository contributor graphs because bots and tools are incorrectly credited for generated work. This introduces unauthorized co-author trailers and session identifiers, violating actual user authorship rights and skewing audit trails.

Can I enforce a git policy to block tool footers and session URLs in commits?

Yes, you can enforce a git policy to block tool footers and session URLs in commits. Cross-agent enforcement applies to all pipeline agents across target repositories, workspace repositories, and brain-seedbank forks to guarantee strict user-only authorship.

Does this bot attribution blocking work across all workspace repositories and forks?

Yes, this bot attribution blocking works across all workspace repositories and brain-seedbank forks. It applies to all commits created by pipeline agents across target repositories to enforce strict user-only authorship policies.

What's the best way to keep AI workflow commit history accurately reflecting human contributors?

The best way to keep AI workflow commit history accurately reflecting human contributors is to apply an attribution policy that blocks bot identity overrides and co-author trailers. This ensures audit trails remain clean and contributor graphs stay meaningful for development teams.