Uh oh!
There was an error while loading. Please reload this page.
chore: add Claude Code automations (skills, subagent, spec-drift hook) - #29
Merged
Conversation
Add two user-invocable skills (changelog-entry, new-resource), a filter-provider-reviewer subagent for the ES filter/provider layer, and a Stop hook that warns when an Api/Dto resource changed without regenerating public/spec.yaml (which CI's api-spec.yml would otherwise fail on). The Elasticsearch MCP from the automation review was intentionally left out: it is the only recommended item needing an external runtime, the sibling event-database-imports repo did not adopt one, and ad-hoc ES access via `docker compose exec phpfpm curl` covers the need with no new dependency.
✅ No changes detected in API specification |
…laude-automations # Conflicts: # CHANGELOG.md
Base automatically changed from
feature/adapt-claude-setup-from-imports to
developJuly 7, 2026 09:25
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add the zero-dependency automations from the automation review. Stacked on #28 (shares the
settings.jsonStop block) — review/merge #28 first, then this retargets todevelop.Changes
.claude/skills/changelog-entry/(user-invocable) — add the CHANGELOG[Unreleased]entry in the CI-enforced format (.github/workflows/changelog.yaml), with explicit guidance to match the terse house tone..claude/skills/new-resource/(user-invocable) — scaffold a new ES-index-backed resource following the DTO + provider + filter pattern, usingEventas the template..claude/agents/filter-provider-reviewer.md— subagent that reviewssrc/Api/Filter/ElasticSearch/andsrc/Api/State/changes for query-DSL correctness, filter-vs-sort separation, and index-contract alignment.scripts/claude-hook-check-spec-drift.sh+Stophook — warn when ansrc/Api/Dto/*resource changed butpublic/spec.yamlwas not regenerated (which CI'sapi-spec.ymlwould fail on).CLAUDE.md— list the new skills/subagent/hook in the automation section.Why
These four items came out of the automation-recommender review and, unlike the Elasticsearch MCP it also suggested, need no external runtime — they're pure repo files. They target this repo's real friction points: the CI-enforced changelog format, the rigid resource-scaffolding pattern, the raw-ES-DSL filter code, and spec drift.
Deliberately excluded
event-database-importsrepo did not adopt one, and ad-hoc ES access viadocker compose exec phpfpm curl http://elasticsearch:9200/...covers the need with no new dependency. Can be added later as a one-linedocker runMCP entry if wanted.Note
.claude/skills/*and.claude/agents/*markdown isn't covered by CI'smarkdownlint '**/*.md'(hidden-dir glob), matching the existingupdate-api-specskill.