Loading...
Loading...
Found 10,569 Skills
Challenges stakeholder requests to identify real needs and propose optimal solutions. Use when receiving vague feature requests, reframing a problem before implementation, or when user mentions problem framing, XY problem, stakeholder request, or solution discovery. WHEN NOT: Well-defined technical tasks with clear requirements, bug fixes with known root causes, or routine CRUD operations.
Use when planning a multi-article content strategy from a research corpus, creating domain maps for content topology, building production plans for pillar and cluster articles, or tracking cross-article production.
Walk through a Jira task plan and interactively confirm assumptions, resolve open questions, and validate decisions — using progressive disclosure. Only asks questions relevant to the CURRENT phase or task being executed. Use when the user says "review the plan", "ask me questions", "clarify assumptions", "let's go through the questions", "grill me on the plan", "validate plan for PROJECT-1234", or anything about reviewing, questioning, or validating a task plan. Also triggered by the orchestrating-jira-workflow skill as Phase 3 of the pipeline, and re-invoked during Phase 5 before each task execution. Requires a task plan at docs/<TICKET_KEY>-tasks.md.
A validation framework that ensures Claude's responses are current, accurate, complete, and clear. Use this skill whenever the user asks a factual or research question, requests analysis or recommendations (e.g., "What's the best framework for X?", "Compare options for Y"), or any prompt where recency and accuracy matter. Also trigger when the user explicitly asks for validated, verified, or fact-checked answers. This skill should activate broadly — if the answer depends on facts that could have changed in the last few months, use it. Even questions that seem straightforward ("Is X still the recommended approach?") benefit from this skill's validation pipeline. Do NOT trigger for purely creative writing, casual chat, or tasks that are entirely opinion-based with no factual claims.
Use Claude Code to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
Run Gemini CLI review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Complete GitHub pull requests by iterating on CI and review feedback until the PR is ready.
Run Codex, Claude Code, and Gemini CLI reviews against the current branch concurrently, deduplicate the findings, and fix only the review comments that are still valid for the current codebase.
Fetch a GitHub pull request body and its messages for the current repository.
Inspect unresolved review threads for the current pull request, then reply to and resolve them as needed.
Use Codex to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
Run Claude Code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.