feat(skills): add essentials-sync skill - #135
Merged
Merged
Conversation
Wrap the essentials-sync CLI in a thin ess/ skill so the extract-and-sync workflow is available to any agent, not just from a shell in this repo. The skill adds only what the CLI lacks: a resolver that finds the binary once the skill has been installed into another repo (ESSENTIALS_SYNC_BIN, PATH, ESSENTIALS_REPO, then the in-repo path), and a dry-run-then-approve gate, since a real run writes to two working trees. All scanning, extraction, and review logic stays in the CLI; run.sh forwards its arguments verbatim.
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.
Wrap the essentials-sync CLI in a thin ess/ skill so the extract-and-sync workflow is available to any agent, not just from a shell in this repo.
The skill adds only what the CLI lacks: a resolver that finds the binary once the skill has been installed into another repo (ESSENTIALS_SYNC_BIN, PATH, ESSENTIALS_REPO, then the in-repo path), and a dry-run-then-approve gate, since a real run writes to two working trees. All scanning, extraction, and review logic stays in the CLI; run.sh forwards its arguments verbatim.