Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation and for every rewrite of an existing issue's body — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without…
Draft a TIL-style blog post in the user's voice and write it to Notion with Status="Claude Draft". Contains voice guide for matching the user's writing style. Use when user approves a TIL topic and wants a draft created.
Fetches and processes GitHub pull requests waiting for review. Returns fully formatted markdown with PRs grouped by category (Feature/Bug, Chores, Dependency Updates) and sorted by age. Includes metadata like CI status, review status, size metrics, and viewing history. Use when user wants to see their PR review queue.
Scans GitHub commit history for commits that might make good TIL blog posts. Queries all your repos across all orgs via GitHub API. Tracks assessed commits in Notion to avoid duplicates across machines. Use when user asks for TIL ideas from their recent work.
Confirm we have actually completed and validated what we planned to accomplish. TRIGGER whenever the user asks you to confirm a task is complete, if any implementation or validation was missed, etc.
Use to see or verify anything a web browser shows - that a page or UI change renders, console errors, clicking through a flow, screenshots. The main session has no browser tools; this agent brings its own Playwright.
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
Use this agent for ALL Notion API operations (create, search, fetch, update). Never use Notion MCP tools directly. Triggers include notion, writing database, create page, search workspace, fetch page, update page, query database.
Posting a comment or review is not reversible the way editing a file is. Every comment creation notifies whoever's watching the PR/issue, and it stays in the timeline even if you fix it a moment later. So a "test comment" to check the command works, followed by a real one, followed by a "sorry, ignore the above" — is…
Diagnose Argo CD application health, sync status, and deployment issues. Use when troubleshooting application deployments, checking sync status, viewing resource health, or identifying configuration drift.
Take a ticket whose approach and design are already approved through implementation, review and evidence to a draft PR, with nobody watching. Escalates decisions on the ticket and stops rather than choosing.
Plan a ticket with nobody watching. Three independent discuss runs are reconciled into one approach and three design runs into one design, both are posted on the ticket, and implement-unattended is started in a new tmux window. Escalates on the ticket rather than taking a one-way decision.
Jira gotchas for the Atlassian MCP tools. Covers the cloud ID that works, reads that silently omit comments, fields and paging that make responses too large or incomplete, and markdown that Jira's conversion breaks in posted comments and descriptions. Read before every Jira tool call, reads included, because a bad…
★not rated 24 todayA82 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: