| name | agent-recall-compiler-maintainer |
| description | Maintain voku/agent-recall-compiler package source, tests, docs, prompt output, manifest loading, scope selection, outcome logging, and local vendor syncs in consuming projects. |
Agent Recall Compiler Maintainer
Use this skill when changing the voku/agent-recall-compiler package itself. Keep package behavior generic and deterministic; consuming-project conventions belong in config, examples, or tests.
Fast Path
- Inspect
git status --short and the relevant package source before editing.
- Preserve source-package authority: package repo first, consuming-project
vendor/voku/agent-recall-compiler only for local integration testing.
- Keep selection deterministic: active guidance and constraints are selected by scope overlap and validated metadata, not by semantic similarity.
- Treat compile blockers as intentional safety behavior. Add tests before relaxing any blocker.
- Add focused regression tests for manifest loading, config path resolution, scope selection, prompt output, validation-plan output, or outcome logging when those change.
- For guidance event changes, verify compile output includes
compilation_id, evaluated_guidance, and per-guidance guidance_outcomes, and verify log-outcome appends both JSONL event types transactionally.
- Validate from the package repo.
Validation
vendor/bin/phpunit
vendor/bin/phpstan analyse --configuration=phpstan.neon.dist
When testing inside a consuming project, separately report those integration commands and do not treat them as a substitute for package tests.
