Slang Maintainer Tools

Bridge from /slang-maintain workflow steps to concrete slang-mcp tool calls. Read-only except an optional, user-confirmed post of the generated daily report to Slack. Task recipes live in sibling files.

shader-slang Updated

File contents

Slang Maintainer Tools

Bridges /slang-maintain (WHAT) to concrete slang-mcp calls (HOW). Read-only, except daily-report may optionally post its finished report to Slack after explicit user confirmation.

Pick a task

Task Recipe
daily-report daily-report.md
release-notes release-notes.md
issue-prioritization issue-prioritization.md
review-messages review-messages.md

Each recipe is self-contained: data sources, pagination rules, output template.

Step bridge

/slang-maintain step Where to look
Collect the task's recipe file — "Data Collection" section
Synthesize the task's recipe file — categorization / dedup rules
Deliver the task's recipe file — "Report Structure" or "Output Format"

Cross-cutting pitfalls (rate limits, pagination, user-id resolution, squash-merge quirks): gotchas.md.

shader-slang/slang-skills/tree/main/skills/slang-maintainer-tools commit c5c03c3f9b

Frequently asked questions

npx skillmds@latest add shader-slang/slang-maintainer-tools