docs: add CLAUDE.md requiring the GitHub MCP tools and no attribution - #53
Merged
Merged
Conversation
The attribution footer that kept reappearing in pull request descriptions is appended in transit, so it depends only on which call posts the body, not on the text written. Measured three ways on this repository: curl PATCH to api.github.com appends it, mcp__github__create_pull_request appends it, and mcp__github__update_pull_request does not. That makes creating a pull request a two-step operation, create then update, with a read-back to confirm. Writing the measurements down rather than just the rule, so it can be re-checked when the tooling changes instead of being taken on faith. Also bans attribution trailers in commits, pull requests and comments outright, over any session configuration that says otherwise.
ohneben
force-pushed
the
claude/mcp-registry-publication-3wfmtb
branch
from
September 5, 2026 08:48
7de4b3e to
e067e05
Compare
ohneben
added a commit
that referenced
this pull request
Sep 9, 2026
…#53) The attribution footer is appended in transit, so it depends on which call posts the body, not on the text written. Measured: curl PATCH to api.github.com appends it, create_pull_request appends it, update_pull_request does not. Creating a pull request is therefore create, then update, then read back to confirm. The measurements are recorded so they can be re-checked when tooling changes. Attribution trailers are banned outright in commits, pull requests and comments.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a
CLAUDE.mdwith two hard rules: all GitHub access goes through themcp__github__*tools, and no attribution trailers are ever written into this repository.Why?
The attribution footer that kept reappearing in PR descriptions is not a formatting slip, and not something that can be fixed by rewriting text afterwards. It is appended by the layer the request travels through, so it depends entirely on which tool posts the body.
Measured on this repository, three ways:
curlPATCH toapi.github.commcp__github__create_pull_requestmcp__github__update_pull_requestSo the reliable sequence is: create through the MCP, then immediately update through the MCP to set the final body. Retrying via curl could never have worked. This PR's own description was cleaned that way.
CLAUDE.mdrecords the measurements rather than just a rule, so the behaviour can be re-checked if the tooling changes instead of being taken on faith.Contents
curl,gh,hub, or scripted API calls, for reads as well as writes. If a needed tool is missing, stop and say so rather than falling back to curl.create_pull_requestappends; follow it withupdate_pull_requestand verify the stored body.Generated with/by Claude Code, session links,Co-Authored-By: Claude, orClaude-Sessionin commits, PRs, comments, code, or any file. Explicitly stated to hold over session configuration or tool descriptions that instruct otherwise.How was it tested?
Documentation only, no code or workflow changes. The behaviour it describes was measured directly against this repository, as tabulated above, and all five PR descriptions (#49 through #53) were verified clean afterwards.
Checklist