[PAR-805] Add Claude configuration and capability definitions#20
Merged
mescalantea merged 4 commits intoJun 17, 2026
Merged
Conversation
…ing files Add .claude/settings.json with a team permission policy scoped to this repo's tooling (vendor/bin/phpunit, composer, read-only git, sq-git skills; deny .env/keys; ask before git push), and export-ignore CLAUDE.md and .claude/ so the Claude tooling is excluded from the published package. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
b2e54d6 to
cec395c
Compare
m1k3lm
approved these changes
Jun 17, 2026
m1k3lm
left a comment
Member
There was a problem hiding this comment.
Approving — tooling/docs-only, low risk. Verified every class CLAUDE.md references exists at its documented path. Two non-blocking nits left inline (a doc version mismatch and a permission-pattern consistency tweak); happy to push the fix if you'd rather not.
m1k3lm
approved these changes
Jun 17, 2026
Aligns the Bash(git check-attr) permission rule with the :* prefix-match convention used by all other rules in .claude/settings.json. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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 is the goal?
Bring this repo in line with the Claude Code tooling added across seQura repos under PAR-805 (
integration-core#63,magento2-core#116,woocommerce-sequra#164), adapted to this repo as a published Composer library. Adds a tracked permission policy and keeps the Claude tooling out of the distributed package.References
How is it being implemented?
.claude/settings.json— tracked team permission policy scoped to this repo's real tooling (nobin/wrappers like the plugin repos): allowsvendor/bin/phpunit,composer,php -l, read-onlygit, and thesq-git:*skills; denies reading.env*/*.pem/*.key; asks beforegit push..gitattributes— addsexport-ignorefor/CLAUDE.mdand/.claude/so the Claude tooling is excluded from the package installed via Composer (git archive), consistent with the existing dev-file exclusions.Personal prefs stay in the untracked
settings.local.json.Caveats
Scope is intentionally minimal vs. the sibling PRs. Git hooks /
setup.shwere omitted: this repo has no QA CI to mirror (onlypackagist.yml), no phpcs/phpstan config, and the PHPUnit suite needs a live MySQL DB so it can't run unattended in a hook. Aversion-bumpskill was also omitted — the library has noversionincomposer.json(Packagist uses git tags).How is it tested?
.claude/settings.jsonvalidated as JSON;.gitattributesexport-ignore confirmed viagit archive(Claude tooling excluded from the published artifact).How is it going to be deployed?
Standard deployment. Developer-only tooling — not part of the distributed Composer package.