chore: add the code-review and cleanup skills used for the unslop pass 6b064615 days ago 17 lines · 1.3 KB 1 # Source playbooks 2 3 The why skill spawns one investigator per available evidence category, each reading a single source-specific playbook below. The playbooks are concrete examples for common MCPs. Adapt them for a different MCP in the same category. 4 5 | Category | Playbook | Example MCP it documents | 6 |---|---|---| 7 | Source control history | [ ` code-archaeology.md 8 | Issue / ticket tracker | [ ` linear.md 9 | Long-form documents | [ ` notion.md 10 | Real-time team chat | [ ` slack.md 11 | Infrastructure observability | [ ` datadog.md 12 | Error / exception tracking | [ ` sentry.md 13 | Product analytics warehouse | [ ` databricks.md 14 15 Cross-cutting: 16 17 - [ ` incident-postmortem.md `
`
]
(
./sources/code-archaeology.md
)
|
git,
`
gh
`
|
`
]
(
./sources/linear.md
)
|
Linear (adapt for Jira, GitHub Issues, Plane, Shortcut)
|
`
]
(
./sources/notion.md
)
|
Notion (adapt for Confluence, Google Docs, Coda)
|
`
]
(
./sources/slack.md
)
|
Slack (adapt for Discord, Microsoft Teams, Mattermost)
|
`
]
(
./sources/datadog.md
)
|
Datadog (adapt for New Relic, Honeycomb, Grafana, Splunk)
|
`
]
(
./sources/sentry.md
)
|
Sentry (adapt for Rollbar, Bugsnag, Airbrake)
|
`
]
(
./sources/databricks.md
)
|
Databricks SQL (adapt for Snowflake, BigQuery, ClickHouse, dbt)
|
]
(
./sources/incident-postmortem.md
)
. Add this if the target code looks defensive (null checks, retry, timeout, rate limit, feature flag, egress guard, OOM handler).