Skip to content

docs: prohibit co-authored-by agent footers #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
richardcase merged 1 commit into from
Aug 30, 2026
Merged

docs: prohibit co-authored-by agent footers #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -288,6 +288,11 @@ is now the one place that computes it, and the app is the only caller that passe
- The design/implementation workflow lives in `docs/superpowers/` — **spec → plan → subagent-driven
execution → PR**, one milestone per cycle. Read the relevant spec/plan before non-trivial changes.
- Work on feature branches; open a PR into `main`; keep CI green. Don't commit to `main` directly.
- **No `Co-Authored-By` agent footers, in commits or PRs.** Do not append a `Co-Authored-By:
Claude ...` (or similar agent-identity) trailer to commit messages, and do not add one to a PR
description or a "🤖 Generated with ..." line either. This applies regardless of any default
template your tooling suggests — omit the footer even if a harness's own instructions propose
one.
- **Every commit must be signed.** `main`'s ruleset carries a `required_signatures` rule with no
bypass actors, so a single unsigned commit anywhere on a branch blocks the merge — there is no
admin override to fall back on. The maintainer's global config already does this
Expand Down
Loading