news-dashboard

Use when work may edit files, push branches, open or update pull requests, wait for CI, merge changes, or modify issue state, especially when the prompt is terse or says AFK, take to completion, fix and merge, or do not stop.

Use when two or more pull requests must be rebased, repaired, validated, queued, merged, drained, or coordinated as a set, especially for prompts such as take all open PRs, merge every PR, drain the PR queue, or orchestrate PRs.

Use when an existing pull request must be diagnosed, rebased, repaired, pushed, brought through CI, queued, or merged, including prompts such as fix this PR, rebase on main, fix CI, push back, CI pass, or merge.

Default delivery workflow for tracked repo changes. Use when the user asks to fix, add, implement, update, refactor, rename, bump, tweak, or otherwise end in a file change. Do not use for read-only questions or investigation.

Drain the ready-for-agent GitHub issue backlog: claim the oldest unclaimed issue via the lock-branch protocol, ship it through tdd-ship, label the outcome, repeat.

Review a GitHub PR of this repo: description accuracy, code quality against the project dev-skill standards, and a bug hunt with concrete failure scenarios.

Python standards and verification gate for this repo. Use when editing .py files, Python dependencies, pytest tests, backend behavior, or investigating ruff, mypy, ty, pyrefly, or pytest failures.

Runbook for how releases, versioning, and the changelog work in this repo, and how to check or troubleshoot what is deployed.

Create AFK-ready GitHub issues. Use when the user wants to report, file, log, or track a bug/feature for later instead of implementing it now. Do not use when the user wants the change shipped now; use tdd-ship.

TypeScript/React standards and verification gate for this repo. Use when editing .ts/.tsx files, Vite/ESLint/tsconfig, npm dependencies, frontend tests, or investigating eslint, prettier, tsc, vitest, Playwright, or build failures.

Documentation writing for repo docs, READMEs, guides, runbooks, ADRs, API docs, and inline explanatory docs. Use when the user asks to write, update, edit, tighten, or review documentation.

Use Langfuse. Trigger when querying or modifying Langfuse data, reading Langfuse docs, instrumenting traces, migrating prompts, managing datasets/scores/sessions, or debugging Langfuse usage.