Menu
Asks Copilot CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guided development workflow that orchestrates planning, review, implementation, testing, and rule maintenance. Use this skill whenever the user wants to develop a feature, fix a bug, refactor code, or make any code changes following a structured process — even if they don't explicitly mention "workflow" and simply describe what they want built or fixed.
Check code changes for .claude/rules/ compliance. Use this skill when you need to verify that code changes follow project coding rules, whether as part of dev-workflow or standalone. Triggers on: rule compliance check, rules review, verify conventions, check coding standards. Best suited for hard rules (naming, imports, placement, explicit prohibitions); intent-style rules are checked on a best-effort basis.
Consult with a peer engineer for plan review, code review, implementation discussions, or problem-solving brainstorming. Use when you need a second opinion, want to validate your approach, or check for overlooked issues.
Asks Codex CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
Review uncommitted diff for content unsuitable for publication to a public repository — secrets/credentials, user-specific absolute paths, internal-only URLs/hostnames, and personal identifiers. Each iteration dispatches a fresh subagent that returns findings; the main thread applies the subagent's mechanical fixes and re-dispatches until the subagent declares no remaining findings or max iterations is reached. Non-interactive — no user prompts. Use as a final gate before publishing changes; designed to be called from non-interactive routines such as dev-workflow's hooks.on_complete or dev-workflow-triage's per-Finding sub-flow.
Refactor verbose or unnatural natural-language prose — code comments, test descriptions, docstrings, user-facing text — into concise, native-sounding prose in a configured target language, using a sonnet subagent by default. Two modes: file mode rewrites a file's target-language prose in place; text mode returns the refactored text. Preserves code, identifiers, and proper-noun terms while translating ordinary technical vocabulary into the target language. Non-interactive — no user prompts. Use after generating prose with a model prone to verbosity, or to polish text before presenting it.
| name | ask-copilot |
| description | Asks Copilot CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks. |
| allowed-tools | Bash(copilot *) |
Executes the local copilot CLI to get coding assistance.
Note: This skill requires the copilot CLI to be installed and available in your system's PATH.
Run a single query with -p (prompt mode):
copilot -p "Your question or task here" --allow-all-tools
| Option | Description |
|---|---|
-p | Non-interactive prompt mode (required for scripting) |
--model MODEL | Specify model (e.g., claude-sonnet-4.5, gpt-5, gpt-5-mini) |
--allow-all-tools | Auto-approve all tool executions (required for -p) |
--continue | Resume the most recent session |
For all available options, run
copilot --help
Ask a coding question:
copilot -p "How do I implement a binary search in Python?" --allow-all-tools
Use a specific model:
copilot -p "Review this code for potential issues" --model gpt-5 --allow-all-tools
Let Copilot make changes automatically:
copilot -p "Refactor this function to use async/await" --allow-all-tools
Continue a previous session:
copilot -p "Now add error handling to that function" --continue --allow-all-tools
-p flag runs Copilot non-interactively and requires --allow-all-tools--model to switch models