deploylisted

# Deploy Read `.claude/project-profile.md` for the commands **and the permissions**. If it is missing, stop: this skill runs commands that affect things outside the working tree, and guessing them is not acceptable. ## Permissions come first The profile records three separate answers. Honor each one, and when the profile does not say, take the cautious reading and ask. | Action | Default when unspecified | |--------|--------------------------| | Commit | Ask, showing the message first | | Push | Ask, showing the branch and commit list | | Deploy | Ask, showing the target | Two hard rules that no profile setting overrides: - **Never force-push, never rewrite published history, never push to a protected branch.** If the profile names branches that must not be pushed to directly and the current branch is one of them, stop and offer to create a branch instead. - **Never deploy a build that did not pass.** There is no "the failure is unrelated" exception; if it is unrelated, it is still a red build going to production. If secrets are needed for a step, they come from the environment. Never read a secret into the transcript, never inline one into a command, never write one into a file. ## Pipeline Stop at the first failure. Report where you stopped and what state things are in, which is the part that matters when something breaks halfway. ### 1. Preflight - `git status`: know what is uncommitted before touching anything. - Confirm the current branch is one the prof