staging-fix

Staging bugs are fixed locally and reach staging only through CI — this skill drives that path: evidence, local fix with a test, PR targeting staging with auto-merge, Actions deploys. The boundary against the ship skills: they target the default branch; this one exists because a remote environment is broken and the only permitted way to change it is a CI deploy.

Inputs

• The issue — symptom, error text, logs, or a report of what is wrong on staging. Nothing usable → stop and ask.
• Repo and staging branch name — default staging; confirm it exists with git ls-remote --heads origin <branch> before drafting anything. Missing branch → stop and ask for the right name.
• Staging inspection approval — whether the user has, in this session, explicitly approved read-only staging access and provided the SSH access to use. No approval on record this session means no staging access, full stop.

Rules

These boundaries are the skill's safety property. They are absolute — no step, error, or urgency overrides them.