docs(edge-delivery-services): lead five skill descriptions with their trigger - #318
Closed
LuizFrareWJ wants to merge 5 commits into
Closed
docs(edge-delivery-services): lead five skill descriptions with their trigger#318LuizFrareWJ wants to merge 5 commits into
LuizFrareWJ wants to merge 5 commits into
Conversation
…dobe#215) Moved the trigger ahead of the 'Reference for...' noun phrase. The scope, the aem up failure modes and both da-content / content-driven-development redirects are unchanged, only reordered. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…his-when trigger (adobe#215) Replaced the 'Apply a ... process' opening with the trigger, kept the ALL-code-changes scope and turned the excluded cases into an explicit do-not-use clause. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
adobe#215) Moved 'Use this skill whenever...' to the front, kept the onboarding scope and the page-import / content-driven-development redirects already documented in the body. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
adobe#215) Moved the trigger ahead of the capability summary and kept the migrate/migration/migrating aliases plus the snowflake disambiguation intact. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… trigger (adobe#215) Moved the trigger list ahead of the 'Create or edit...' opening; the three JSON config files are now named in the Covers clause. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Author
|
Per CONTRIBUTING.md: this PR was co-authored with an AI tool and should carry the |
Author
|
Superseded by #320 — reopening from my personal account (@LuizFrare), which is the correct identity for this contribution. Same commits, same content. Sorry for the noise. |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow-up to #215.
Context
#215 already got its sweep. All 19 skills in its two tables were fixed on 6 July, one PR per skill (#241, #244, #245, #246, #248, #249, #250, #251, #254, #258 and siblings), and
x-searchhas since been removed from the plugin. As far as I can tell #215 can be closed — this PR does not reopen its scope.What it does cover is five skills in the same plugin that show the exact pattern #215 describes but were never in its tables. Four open with a capability statement instead of a trigger;
content-driven-developmentopens with "Apply a Content Driven Development process".Changes
Each description now follows the shape the sweep established:
aem-clicontent-driven-developmentcreate-sitepage-importue-component-modelNo information was dropped. Every scope note, trigger alias and sibling redirect already present in these descriptions is preserved — the
migrate/migration/migratingaliases and thesnowflakedisambiguation onpage-import, theda-contentandcontent-driven-developmentredirects onaem-cli, thepage-importredirect oncreate-site— only reordered so the trigger leads.Versions are untouched; semantic-release owns those.
One commit per skill, matching both the granularity of the original sweep and each skill's own
.releaserc.json.Verification
npm run validatepasses (166 skills, exit 0).