Skip to content

feat(meta-mode): validate project playbook extensions - #28

Merged
3metaJun merged 2 commits into
mainfrom
feat/meta-mode-playbook-validation
Oct 5, 2026
Merged

3metaJun merged 2 commits into
mainfrom
feat/meta-mode-playbook-validation

Conversation

@3metaJun

@3metaJun 3metaJun commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Problem

Project playbooks can extend the bundled meta-mode playbooks, but stale step anchors and missing bases were only detected when an agent tried to use them. A mstack upgrade could therefore leave a project workflow silently out of sync.

Scope

  • Add tools/meta-mode/check-playbooks.mjs for deterministic project-playbook validation.
  • Validate when:, extends:, and straight-quoted After, Before, Replace, and In anchors.
  • Document the checker in README.md, tools/meta-mode/README.md, and skills/meta-mode/SKILL.md.
  • Add focused CLI and behavior tests and update the reviewed baseline manifests.

Verification

  • npm test
  • node scripts/skill-baseline.mjs --check
  • npm run check-playbooks -- .
  • npm pack --dry-run --json

Agent: GPT-5 via pi

3metaJun and others added 2 commits October 5, 2026 12:46
- Fail on a missing project root or bundled directory instead of passing.
- Accept BOM and unterminated frontmatter; resolve extends stems case-sensitively
  and only inside the bundled directory.
- Use the <meta-mode-tools> placeholder and --bundled in the skill command so it
  works with an artifact destination override; document list-item changes.
- Resolve the test script from the file location, skip the symlink test when
  symlinks need privileges, and cover the default bundled path.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@3metaJun
3metaJun merged commit 115e62e into main Oct 5, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant