devops-release-scopelisted
Install: claude install-skill th3r-dev/th3-skills
# devops-release-scope
One command collects the facts; the agent does the judgement and the wording.
```bash
S=skills/devops/release-scope/scripts
uv run $S/release_scope.py --to v1.2.22 --prod v1.2.21,v1.2.21.1 \
--repo api=../backend=org/backend --repo web=../frontend=org/frontend \
--key-regex '(?:PRJ|ISS)-\d+' --mirror-regex '^\[(PRJ-\d+)\]' \
--board tracker=work/jira/<date>/tracker/issues.json --board mirror=work/release/v1.2.22/mirror.json \
--out work/release/v1.2.22 # -> scope.md + scope.json (--selftest checks the joins)
```
Branch names: `--to` / `--prod` without a slash get `--release-prefix` (default `origin/releases/`);
`--dev` defaults to `origin/develop`. Each `--repo` is a local clone with an `origin`; the GitHub
slug is optional and only feeds `gh pr list`.
## 0. Baseline: what prod runs
`--prod` is every branch prod's images were built from. **The owner states this, not git** — a
hotfix branch that was cut but never deployed must not be a base. When the owner says prod moved,
change `--prod`. Never infer it from tags or from what a staging environment runs.
## 1. Refresh the boards
Export each board to JSON before running (Jira REST `search` output, the Rovo `{issues:{nodes}}`
shape, or a JSON list of pages — the script reads all three). A mirror board that copies tickets
from another tracker as `[KEY] summary` is merged onto the source key through `--mirror-regex`.
Pages too big for the context go straight to disk and are combined