You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLAUDE.md: the managed repo-setup block (library, Go, make check, SemVer tags, Claude may commit, taskd project rypt) plus a Branching section. The global rules assume GitHub Flow into main; this repo sends feature PRs to development, so the section overrides that.
Makefile: a check target that runs vet test, so the default pre-commit check make check works.
.claude/settings.json: allows git commit, git push, and gh pr create/view/checks, and enables the gopls-lsp plugin.
.claude/claude-security-guidance.md: the threat model the security-guidance reviewers read. It covers trust boundaries (API responses and caller arguments), where secrets come from, and the token, redirect and server-text rules the client already enforces.
.claude/repo-setup.json: the repo-setup state file (rules version 1). The initial security scan is recorded as pending.
Separately, repo-setup created the GitHub ruleset "repo-setup: default branch" on main and development. It requires PRs with review threads resolved, the test/lint/vulncheck checks, and Copilot review on push, and it blocks deletion and force pushes. That change is already live and isn't part of this diff.
Why
These files set up Claude Code for this repo: the check command, the commit policy, and the branch flow from CONTRIBUTING.md.
Testing
make check passes locally (go vet with and without the integration tag, the gofmt check, unit tests). No Go code changed.
Record this repo's working rules so Claude Code follows them: the
check command, the commit policy, and that feature branches and pull
requests target development rather than main. The new make check
target runs vet and test, so the default pre-commit check works here.
The threat model in .claude/claude-security-guidance.md feeds the
security-guidance reviewers. It names the token, redirect and
server-text rules the client already enforces.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The allow rules let Claude push and commit without a prompt, but their
wildcards also approved forms that run commands (--receive-pack,
--exec), rewrite or delete remote refs (--force, --delete, --mirror,
--prune, colon refspecs), or skip hooks (--no-verify). Deny rules take
precedence over allow rules, so those forms are now refused while
ordinary pushes still need no prompt.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The commit permission must block git commit -n before approval.
No open issues 🎉
1 previously missed issue
In code that hasn't changed since last review
Block short -n form of git commit --no-verify
.claude/settings.json:4
The allow rule still auto-approves the short git commit -n form of --no-verify, because the deny list only matches the long option on line 20. Claude can therefore bypass commit hooks while this configuration grants unattended commits; add deny patterns covering -n wherever it appears (or avoid the blanket commit allow).
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
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 changed
CLAUDE.md: the managed repo-setup block (library, Go,make check, SemVer tags, Claude may commit, taskd projectrypt) plus a Branching section. The global rules assume GitHub Flow intomain; this repo sends feature PRs todevelopment, so the section overrides that.Makefile: achecktarget that runsvet test, so the default pre-commit checkmake checkworks..claude/settings.json: allowsgit commit,git push, andgh pr create/view/checks, and enables thegopls-lspplugin..claude/claude-security-guidance.md: the threat model the security-guidance reviewers read. It covers trust boundaries (API responses and caller arguments), where secrets come from, and the token, redirect and server-text rules the client already enforces..claude/repo-setup.json: the repo-setup state file (rules version 1). The initial security scan is recorded aspending.Separately, repo-setup created the GitHub ruleset "repo-setup: default branch" on
mainanddevelopment. It requires PRs with review threads resolved, thetest/lint/vulncheckchecks, and Copilot review on push, and it blocks deletion and force pushes. That change is already live and isn't part of this diff.Why
These files set up Claude Code for this repo: the check command, the commit policy, and the branch flow from CONTRIBUTING.md.
Testing
make checkpasses locally (go vet with and without the integration tag, the gofmt check, unit tests). No Go code changed.🤖 Generated with Claude Code