# See what needs attention without leaving Slack

Ask Warestack for grounded delivery context, review it privately, and share it with the channel only when the team needs it.

- Private responses by default
- Source-aware delivery summaries
- Personal and team attention scopes
- Explicit --public sharing

```bash
/warestack attention team:backend
```

## Attention · backend team

3 pull requests need attention

- Blocked by a failed check
- Waiting on a requested review

Sources · GitHub PRs · Workflow runs · Violations

## Ask, verify, then share

Warestack keeps operational queries low-noise while preserving a clear path from a signal to its source.

1. **Ask in context**  
Run `/warestack attention` for your own authored and requested-review pull requests, or add `team:<slug>` for a team you belong to.

2. **Check the evidence**  
The response groups current attention signals such as failed CI, missing reviews, and unresolved Warestack violations, with links back to the underlying work.

3. **Share intentionally**  
Results are visible only to you unless you add `--public`. Use the flag when the response belongs in the channel conversation.

## Seven commands, with explicit scope

Use the exact forms below after your Slack workspace is connected to a Warestack space.

**Command** `/warestack status repo:<name>`  
Repository snapshot with open pull requests, violations, and the latest workflow run.  
Example: `/warestack status repo:api`

**Command** `/warestack attention [team:<slug>]`  
Pull requests that need action now, scoped to you by default or to one of your teams.  
Example: `/warestack attention team:backend`

**Command** `/warestack violations team:<slug> [severity:<level>]`  
Open team rule violations, optionally filtered by critical, high, medium, or low severity.  
Example: `/warestack violations team:backend severity:high`

**Command** `/warestack activity [team:<slug>]`  
An AI summary of the team’s last 24 hours of pull request activity.  
Example: `/warestack activity team:backend`

**Command** `/warestack assign L-123 @steliosot`  
Assign a synced Linear issue to a teammate whose Slack and Linear identities are linked.  
Example: `/warestack assign L-123 @devg`

**Command** `/warestack whoami`  
Inspect your Slack-to-Warestack mapping, GitHub identity, and team memberships.  
Example: `/warestack whoami`

**Command** `/warestack help`  
Show the available command list and usage examples.  
Example: `/warestack help`

## Quiet by default, scoped to your access

A command response should help you act without unexpectedly adding noise or exposing it to a channel.

### Private unless requested

Every command starts as a private response. Add `--public` to post that result to the channel.

### Identity-aware scope

Personal attention depends on your linked Warestack and GitHub identity. Team attention and activity are limited to your teams; violation results stay within the connected Warestack space.

### One deliberate write command

`/warestack assign L-123 @steliosot` updates the assignee on a synced Linear issue. It requires linked identities; the other commands read and summarize delivery state.