agentleFS
Sign inStart free
agentconfigagentconfig/agentconfig.org/.github/skills/co-author/SKILL.md

co-author

Skill7 starsChanged 3 months agoISCView on GitHub

Manage co-author attribution in commits for agentconfig.org. Use when pair programming, collaborating on changes, or when the user mentions working with another contributor.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Add a Co-authored-by: trailer at the end of commit messages:

    line 17
  2. Distinctive:

    Only human contributors: - Never add AI agents as co-authors

    line 38
  3. Distinctive:

    Verify contributor: - Only use emails from the contributors table above

    line 40
  4. Distinctive:

    Add when appropriate: - When someone contributed ideas, review, or code

    line 41

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

Co-Author Attribution

Contributors

NameAliasesGit Trailer
Jonathan Hoytjon, jonathan, jonmagicJonathan Hoyt <jonmagic@gmail.com>
Francis Brerofrancis, francisfuzzfrancisfuzz <15894826+francisfuzz@users.noreply.github.com>

How to Add Co-Authors

Add a Co-authored-by: trailer at the end of commit messages:

feat(hero): update tagline

Co-authored-by: francisfuzz <15894826+francisfuzz@users.noreply.github.com>

Multiple Co-Authors

For multiple collaborators, add separate lines:

feat(comparison): redesign provider matrix

Co-authored-by: francisfuzz <15894826+francisfuzz@users.noreply.github.com>
Co-authored-by: Jonathan Hoyt <jonmagic@gmail.com>

Rules

  1. Only human contributors - Never add AI agents as co-authors
  2. Use exact format - Co-authored-by: Name <email>
  3. Verify contributor - Only use emails from the contributors table above
  4. Add when appropriate - When someone contributed ideas, review, or code

When NOT to Add Co-Authors

  • Solo work with no collaboration
  • AI-assisted coding (the AI is not a co-author)
  • Minor suggestions from code review (use PR attribution instead)
  • Rebasing or cherry-picking others' commits (original authorship preserved)

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