Add setup skill and How to deploy README section#1
Open
Jerrydiii wants to merge 1 commit into
Open
Conversation
- New .warp/skills/setup/SKILL.md: idempotent setup flow that clones or reuses an existing checkout, verifies required tools, creates .env, guides configuration, and validates credentials - README: add How to deploy section with a copy-pasteable Warp prompt, keep manual steps and rename variable docs to Configuration reference - .env.example: quote values containing spaces so sourcing works Co-Authored-By: Oz <oz-agent@warp.dev>
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.
Summary
setupskill (.warp/skills/setup/SKILL.md) so the agent is usable out of the box: it clones the repo (or reuses an existing clone), verifies required tools andghauth, creates.envfrom the example without overwriting, walks through configuration for only the skills the user plans to run, and validates Slack/Sentry/GitHub credentials — with secrets never pasted into chat or echoed..env.example: quote values containing spaces (RELEASE_CHANNELS,RC_WORKFLOW_NAME) — previouslysource .envbroke on them (found while testing the setup flow).Testing
.envcreation idempotency, sourcing, and all four validation checks (GitHub repo + local checkout pass; Slack/Sentry fail cleanly with blank tokens as designed).Conversation: https://app.warp.dev/conversation/6ed09269-5cf9-4ea1-8922-2bf694cb9892
Co-Authored-By: Oz oz-agent@warp.dev