People can pull the same linked state without leaving Slack. Repository and team tokens both work (repo:org/name or team:slug). Some commands require a team membership in the space.
| Command | Use |
|---|---|
/warestack whoami | Confirm GitHub + Slack (and Linear) identity |
/warestack link | Confirm a Slack binding if whoami shows it is missing |
/warestack status repo:… | Open PRs, attention, latest workflow, violation count |
/warestack violations repo:… | Open rule findings for that repo |
/warestack activity repo:… | Last 24h plus PRs that need action now |
/warestack attention | Personal (or team) action list |
/warestack assign ISSUE @person | Assign a Linear issue to a linked teammate |
/warestack help | Catalog |
/warestack status and /warestack violations should agree with the live card and with the Linear agent on the same issue: linked PR, findings, requested reviewers, CI.
Consistency check
/warestack status and /warestack violations for the same repo:org/name should agree with the live card and the Linear agent on that work:
- A linked feature PR shows its approval finding until evidence-rich human reviews and a later PR event clear it.
- A PR with no stored Linear association shows ticket and test findings, and the card omits Linear.
- The three surfaces use the same stored relationships, not three independent guesses.
Counts can differ across snapshots as checks and reviews arrive. Keep the timestamp and event context instead of forcing two stale answers to match.
Boundaries
/warestack activitysummarizes recent activity; use Events for the underlying timeline./warestack assignis an explicit Linear mutation and requires an attributable linked teammate.- Repository/team tokens must resolve inside the caller’s Warestack space.
- A missing identity, association, or permission is reported; it is not guessed.
Last updated on