Name the deployment skill consistently with its siblings - #20
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR standardizes the Fusion plugin’s deployment sub-skill naming by switching the skill frontmatter name (and all documentation cross-references) from deploy to deployment, aligning it with the existing nominal naming pattern used by the other skills and reducing command-name rewriting ambiguity.
Changes:
- Renames the deployment skill’s frontmatter
namefromdeploy→deployment. - Updates orchestrator routing guidance and cross-skill references to point to
deployment. - Updates README documentation to reflect the new skill name in lifecycle descriptions and the skills table.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| skills/workflows/SKILL.md | Updates routing decision tree and lifecycle instructions to invoke deployment instead of deploy. |
| skills/lookup-files/SKILL.md | Updates “DO NOT TRIGGER” cross-skill guidance to reference deployment. |
| skills/execution/SKILL.md | Updates references instructing users to use deployment for import/release steps. |
| skills/deployment/SKILL.md | Changes the skill frontmatter name to deployment. |
| skills/deployment/references/console-verification.md | Updates reference text pointing to the deployment skill. |
| README.md | Updates skill routing/lifecycle documentation and the skills table to use deployment. |
prvn
previously approved these changes
Aug 5, 2026
stack merge was automatically disabled
August 7, 2026 03:02
Pull Request is not mergeable
stack merge was automatically disabled
August 7, 2026 03:03
Pull Request is not mergeable
stack merge was automatically disabled
August 7, 2026 05:33
Pull Request is not mergeable
mraible
force-pushed
the
fix/deploy-skill-name-consistency
branch
from
August 7, 2026 05:33
0cc7349 to
370ddb3
Compare
The skill declared 'name: deploy' while living in skills/deployment/. Both resolve, so nothing was broken, but 'deploy' was the only imperative verb among six otherwise nominal skill names (authoring, execution, lookup-files, setup, workflows). Renaming the frontmatter to 'deployment' matches the directory and the authoring/execution pattern, and it also removes a cosmetic quirk where the command picker offered :deploy and rewrote it to :deployment on submit. Changing the frontmatter rather than the directory keeps the diff to 15 lines with no path or CI churn, and follows the nominal naming used throughout foundry-skills as well. Updates the 12 references that named the skill 'deploy' across the README, the orchestrator's routing table, and the sibling skills.
mraible
force-pushed
the
fix/deploy-skill-name-consistency
branch
from
August 7, 2026 05:34
370ddb3 to
1bbe957
Compare
prvn
approved these changes
Aug 7, 2026
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
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.
This is not a bug fix. The current setup works: the skill lives in
skills/deployment/and declaresname: deploy, and it resolves and loads correctly either way. This is a naming consistency cleanup, safe to defer or decline.deploywas the only imperative verb among six otherwise nominal skill names:authoringdeployexecutionlookup-filessetupworkflowsauthoring/deployment/executionreads as a consistent trio;author/deploy/executewould too. Mixing one member of the second set into the first is the inconsistency. Nominal naming is also whatfoundry-skillsuses across all ten of its skills.There is a small side benefit: the command picker offered
/crowdstrike-falcon-fusion:deploy(from the frontmatter) but rewrote it to:deployment(from the directory) on submit. With both set todeployment, there is nothing to rewrite.Approach
Changed the frontmatter to
name: deploymentrather than renaming the directory todeploy. The frontmatter route is 15 lines across 6 files; the directory rename would have touched 21 path references across 8 files including CI config, for the same result.Also updates the 12 places that named the skill
deploy: the README skill table and lifecycle prose, the orchestrator's intent-routing table and handoff instructions, and cross-references inexecution,lookup-files, andconsole-verification.md. (authoringalready said "deployment.")Prose using "deploy" as an ordinary verb is left alone.
Verification
./test-validate.sh— 56 passed, 0 failed./test-hooks.sh— 14 passed, 0 failedStacking
Targets
fix/bin-to-scripts(#18) rather thanmain, since #18 modifies four of the same SKILL.md files. GitHub will retarget this tomainautomatically once #18 merges.