chore: add /deploy skill#66
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Adds a
/deployClaude Code skill under.claude/skills/for publishing the userscript to tw-calc.net from the local machine.Why it exists: the CI Deploy
curls the publish endpoint, but WEDOS Global Protection serves an anti-bot (ALTCHA) challenge to datacenter IPs — so GitHub-hosted runners get blocked. A residential IP reaches the endpoint, so runningci/deploy.shlocally publishes the update.The skill captures the process and the gotchas we hit:
@versionmatches — the userscript version comes frompackage.jsonat build time, so a staledist/publishes the wrong script under the right label.REFmust berefs/tags/vX.Y.Z(the script parses the 3rd path segment).TW_CALC_API_KEYis the GitHub secret; the user runs the final command themselves (it's never echoed/committed/put in a transcript).@versionafterwards.It's framed as a workaround: once DNS-direct or a WGP bypass is in place, the normal CI deploy (via
/new-version) handles it, and re-running the failed Deploy run is the CI equivalent.🤖 Generated with Claude Code