Start with what is breaking in the delivery path, not with a feature list. Warestack can observe, explain, route, remind, and preserve evidence across GitHub, Linear, and Slack.
Status on this page is deliberate:
- Available — shipped product surface or authorable template.
- Recommended — a good first enablement, with merge-blocking off.
- Self-serve — configured by the individual, not an admin.
- Not generally available — not a self-serve control yet.
Keep changes tied to intent
| Need | What Warestack does | Use |
|---|---|---|
| Every PR needs a real Linear issue | Requires a Linear association in Warestack’s store — not a key in the branch or Refs: | custom.linear_issue_required · Recommended |
| Someone must own the issue | Checks that the associated ticket is assigned | Rule 7 · Recommended |
| The issue must be active | Checks the Linear workflow states you mark as active | Rule 8 · Recommended |
| The diff must match the ticket | Compares changed files and diff with issue scope and acceptance criteria | Rule 12 · Recommended |
| A PR links the wrong issue | Shows scope drift in the GitHub check, Slack card, Events, and Linear agent context | Rule 12 + worked example |
| A feature spans API, UI, and schema repos | Parent issue for the outcome; one sub-issue and one associated PR per repo. Warestack does not inherit the parent | How to ticket · Recommended |
Raise the review bar without surprising the team
| Need | What Warestack does | Use |
|---|---|---|
| Feature work needs two humans | Counts APPROVED reviews by branch prefix; bots and author do not count | Rule 13 · Recommended |
| “LGTM” is not review evidence | Requires a named command, CI check, or environment result in each counting approval | custom.evidence_in_approval_body · Recommended |
| Review requests sit untouched | DMs the requested reviewer, then the individual repository owner | pull_request_review_sla · Recommended |
| A few reviewers carry the queue | Detects fatigue or reroutes when a reviewer is over capacity | Rule 5 / reviewer_at_capacity · Available |
| Only a bot approved | Nudges for a human review | bot_approval_needs_human · Available |
| Changes requested, then silence | Follows up with the author and escalates | review_feedback_follow_up · Available |
| A draft or open PR goes stale | Flags stale drafts or runs a business-hours follow-up chain | Rule 10 / stale_pull_request · Available |
Keep changes small, testable, and owned
| Need | What Warestack does | Use |
|---|---|---|
| PRs are too large | Applies a configurable size cap with lock-file handling | Rule 1 · Available |
| Commits mix unrelated work | Applies a lines-per-commit atomicity policy | Rule 2 · Available |
| Review should follow branch or path ownership | Routes to named reviewers by prefix or changed path | Rules 3–4 · Available |
| Feature work has no test evidence | Requires relevant test changes or a concrete Testing explanation; generic “N/A” fails | custom.feature_test_evidence · Recommended |
| A large PR has no test files | Comments and adds a needs-tests label | large_pr_without_tests · Available |
| CI/CD changes lack owner review | Detects protected workflow/path changes and can require an owner | cicd_change_without_owner_review · Available; leave its gate off at first |
Put the same facts where people work
| Need | What Warestack does | Use |
|---|---|---|
| Slack needs one source of truth per PR | Creates one live card and updates it in place | pull_request_slack_live_card · Recommended |
| Someone wants a fresh answer in the thread | Request Update replies in that thread, never a second top-level card | Live card · Available |
| A person wants the current queue | Shows Overview › Needs attention: For me / For the space | Overview and attention · Available |
| A reviewer wants a weekday summary | Sends a private snapshot of their own For me queue; skips empty mornings | personal_digest · Self-serve |
| A team asks from Slack | Returns status, violations, activity, attention, identity, or assignment commands | Slack commands · Available |
| A Linear issue needs delivery context | The mention-only workspace agent summarizes linked PRs, checks, reviews, and findings | Linear agent · Available when installed |
| An issue has no linked PR | Returns an honest empty result and asks for a link; never invents owner/repo#n | Worked example |
Understand a change, not just one PR
| Need | What Warestack does | Use |
|---|---|---|
| Browse activity across the space | Filters Events by source and attention, then opens the event detail | Events · Available |
| Audit what changed over time | Shows PR/issue/deployment context, findings, and a per-event timeline | Event detail · Available |
| Review a stack of dependent PRs | Shows GitHub-native or Warestack-detected same-repository stack topology and readiness | PR stacks · Available |
| API + frontend or schema + migrations must move together | Named counterpart-repository evidence is not a self-serve control yet | Cross-repository guards · Not generally available |
Cross-repository stacks are not supported: PR stacks stay inside one repository. Cross-repository guards are a separate, not-generally-available capability.
Follow work through production
| Need | What Warestack does | Use |
|---|---|---|
| Production deploys need release notes | Announces only a successful production / prod deployment, with associated PRs or an unassociated commit | production_rollout_changelog · Recommended |
| A deployment approval is waiting | Nudges the approver and repository owner | deployment_review_waiting · Available |
| Deployment review needs one Slack card | Keeps one card current until the review resolves | deployment_review_live_card · Available |
| Default-branch CI failed | Announces it and can create a deduplicated Linear issue | failed_workflow_default_branch · Available |
Build a sampleable operating record
| Need | What Warestack does | Use |
|---|---|---|
| Security wants a weekly change population | Runs saved SQL on a calendar and announces the result with summary and/or CSV | scheduled_report · Recommended |
| A team needs a custom slice | Natural-language ask → review SQL → preview → save → run history | Reports · Available |
| Leaders need delivery trends | Shows units, previous-window deltas, trends, and repository breakdowns | Metrics · Available |
| Operators need to know what automations did | Shows chain executions and outcomes in Automations › Activity | Automation activity · Available |
| An admin wants evidence before enabling | Replays supported historical PR/review evidence and sends nothing | Dry-run · Available for supported triggers |
Model the organization without inventing one
| Need | What Warestack does | Use |
|---|---|---|
| Start with two isolated repositories | Applies repository-scoped rules and chains | Scope · Recommended default |
| One team owns several repos | Applies team scope while keeping an individual owner per repo | Teams · Available |
| Only one subpath is sensitive | Applies path scope inside selected repositories | Scope · Available where the rule/chain supports changed paths |
| A repo has no reachable owner | Shows ownership readiness and can notify an admin channel | repository_without_owner · Available |
| People need attributable DMs | Confirms GitHub↔Slack identity before person-targeted delivery | People and identities · Available |
| Branch protection must become the gate | Deep-links to GitHub; Warestack does not silently change protection | Repositories · Optional after the observation period |
Choose the next step
- See representative outcomes: See it in action.
- Configure a bounded first pass: Start the pack.
- Let an org AI draft it: For AI agents.
- Browse every stable object ID: Rules catalog and chain kinds.
Last updated on