complete plugin's Write|Edit prompt hooks halt turn continuation on every non-matching edit
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- nextjs
- Domain
- tooling
Research direction
Inspect the complete plugin's three Write/Edit prompt hooks and their matchers, especially the Next.js zone-app condition and the Cosilico repository checks. Reproduce an edit outside those conditions, then trace the command-type path guard using jq. Done means non-matching edits continue without an LLM evaluation while matching files still receive an explicit allow/continue result.
Written by the indexing model from the issue text.
Description
The complete plugin (3.23.0) ships three prompt-type hooks matched on Write|Edit:
- PostToolUse "ARCHITECTURE ENFORCEMENT (Cosilico repos only)"
- PostToolUse "MULTI-ZONE ADVISORY" (Next.js zone-app config files)
- PreToolUse "PRE-WRITE CHECK (Cosilico repos only)"
Because they are prompt hooks with no path pre-filter, every Write/Edit in ANY repo runs an LLM evaluation, and the evaluation's "condition does not apply" verdict surfaces as PostToolUse:Edit hook stopped continuation: This is not a Next.js config file… — halting the agent's turn after each edit. In a long engineering session tonight (populace release work, dozens of edits to Python files), every single edit stopped the turn and required a manual nudge to resume. Same family as the known Cosilico .rac hook misfire.
Fix: gate each prompt hook behind a cheap command-type path guard (jq the file_path, exit 0 fast when the path is outside Cosilico repos / isn't a next.config.*), or convert the repo/path condition into the hook matcher layer, so the LLM evaluation only runs when the file could actually match. The prompt evaluations should also return an explicit allow/continue rather than a bare condition-not-met explanation.
Workaround applied locally: "complete@policyengine-claude": false in enabledPlugins.
- Dominant language
- Python
- Stars
- 32
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/policyengine-claude
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
18 skills/commands still reference old Microsimulation API instead of policyengine.py SimulationOpen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in PolicyEngine/policyengine-claude
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Deltares/imod-python#1940 ·
Maintainers usually reply within 1 day
-
effort: low prio: low ready
Difficulty 1/5 Under an hour Newbie friendliness 82/100
digitalfabrik/integreat-cms#4621 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
netbox status: backlog topic: testing type: housekeeping
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
netbox-community/netbox#23395 ·
Maintainers usually reply within 1 day