#215 block-inventory: add page-import pipeline guard + Use-this-when trigger - #241
Conversation
Tessl Plugin Lint
|
There was a problem hiding this comment.
Pull request overview
Updates the block-inventory skill’s frontmatter description to improve routing and prevent accidental standalone invocation, aligning with the guidance in issue #215 for page-import pipeline sub-skills.
Changes:
- Rewrites the
descriptionto start with a “Use this when …” trigger. - Adds an explicit “Do not invoke directly …” pipeline guard to indicate it’s a
page-importpipeline sub-skill.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| --- | ||
| name: block-inventory | ||
| description: Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions. | ||
| description: "Use this when the page-import pipeline needs to survey the block palette available from a local AEM Edge Delivery Services project and the Block Collection to inform content modeling decisions. Covers returning a block inventory annotated with each block's purpose. Do not invoke directly — called by page-import as a pipeline step." |
|
🎉 This PR is included in version 1.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Addresses #215.
Problem —
block-inventory's description opened with what it does, not when to invoke it, and gave no signal that it is apage-importpipeline step — so an agent could load it in isolation or skip it when routing.Solution — Rewrote the description to lead with a
Use this when …trigger and added an explicitDo not invoke directly — called by page-importguard, per the issue's recommendation for pipeline sub-skills. Content-only change to the frontmatterdescription.Validated with
npm run validate. Generated with AI assistance.Pull Request opened by Augment Code | View session