Menú
Add an item to the project TODO list with t-shirt size categorization (Small, Medium, Large)
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Manages ClaudeChain automated PR chains. Use when working with claude-chain projects, listing open chain PRs, rebasing chain branches, triggering chain workflow runs, checking chain capacity, fetching workflow logs, creating new chains, or updating/editing an open chain PR locally.
Debugging guide for AIDevTools (evals, plan runner, Mac app, PRRadar). Shows how to discover configured repositories, eval cases, artifact paths, plan storage, log files, and CLI commands for troubleshooting. Use this skill when: the user reports a bug, asks to check eval data, shares a screenshot of eval results or the Mac app, mentions a failing case, wants to inspect provider output, needs to debug plan generation or execution, or is debugging PRRadar behavior (pipeline output, rule evaluation, Mac app issues). Screenshots of the Mac app are a strong signal to invoke this skill — they mean the user wants you to reproduce or investigate using the CLI.
Reference for where Claude and Codex provider data is stored on disk — session logs, raw output, thinking/reasoning availability, and format differences between the two providers. Use whenever investigating provider output, debugging missing thinking blocks, reading session history, or asking "where does X get stored for Claude vs Codex?"
Running, writing, and extracting screenshots from UI tests and interactive tests for the AIDevTools Mac app. Use this skill when: running XCUITests, capturing app screenshots, adding new screenshot tests, extracting images from .xcresult bundles, or using the interactive test runner (XCUITestControl) to programmatically drive the app UI.
Guidance for this project's composition root pattern — how SharedCompositionRoot centralises shared service wiring, how the Mac app and CLI targets each have their own root that wraps it, and how platform-specific additions (models, git client, credentials) are layered on top. Use this when adding new shared services, creating a new CLI command that needs services, modifying how providers or credentials are wired, reviewing code that constructs services outside a composition root, or any time someone asks how dependency wiring works in this project.
Guide for adding, modifying, or reviewing configuration in this Swift app. Use when adding credentials or API keys, creating a new config file, adding a ServicePath case, setting up a service that reads settings, wiring configuration through the Apps layer, reviewing whether config is injected correctly (resolved values vs raw services), asking 'where should this config go?', or adding per-repo feature settings. Also use when working with SecureSettingsService, CredentialResolver, SettingsService, DataPathsService, or RepositoryConfiguration anywhere in the codebase.
| name | ai-dev-tools-pr-radar-todo |
| description | Add an item to the project TODO list with t-shirt size categorization (Small, Medium, Large) |
Add an item to the project TODO list at docs/proposed/TODO.md.
$ARGUMENTS) to determine the TODO item title and any detailsdocs/proposed/TODO.md file## Small, ## Medium, or ## Large)- [ ] Item title- [ ] Short item title
Longer description with more context about the idea, rationale,
or implementation notes. Can be a full paragraph.
The TODO file has three sections in this order:
# TODO
## Small
- [ ] ...
## Medium
- [ ] ...
## Large
- [ ] ...
- [ ]