skills/ask-claude/SKILL.md
Asks Claude CLI for coding assistance. Use for getting a second opinion, code generation, debugging, or delegating coding tasks.
npx skillsauth add hiroro-work/claude-plugins ask-claudeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Executes the local claude CLI to get coding assistance.
Note: This skill requires the claude CLI to be installed and available in your system's PATH.
Run a single query with -p (print mode):
claude -p "Your question or task here"
| Option | Description |
|--------|-------------|
| -p | Non-interactive print mode (required for scripting) |
| --model MODEL | Specify model (e.g., sonnet, opus, haiku) |
| --output-format FORMAT | Output format: text, json, stream-json |
| -c, --continue | Continue the most recent conversation |
For all available options, run
claude --help
Ask a coding question:
claude -p "How do I implement a binary search in Python?"
Use a specific model:
claude -p --model opus "Review this code for potential issues"
Get JSON output:
claude -p --output-format json "List the main functions in this file"
Continue a previous conversation:
claude -p -c "Now add error handling to that function"
-p flag runs Claude non-interactively and outputs result to stdout--model is not specified, the default model is usedstream-json outputs responses incrementally as they are generated-p flag skips the workspace trust dialog. Only use in directories you trust.development
Review changed code for reuse, quality, and efficiency, then apply cleanup edits. Dispatches a fresh host-provided reviewer per iteration when available; the main thread applies mechanical edits and re-dispatches until no further edits remain. Non-interactive — no user prompts. Use after implementation as a code-cleanup pass complementary to correctness review.
development
Review changed code for reuse, quality, and efficiency, then apply cleanup edits. Dispatches a fresh host-provided reviewer per iteration when available; the main thread applies mechanical edits and re-dispatches until no further edits remain. Non-interactive — no user prompts. Use after implementation as a code-cleanup pass complementary to correctness review.
development
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.
development
Extract project-specific coding rules and domain knowledge from existing codebase, generating markdown documentation for AI agents. Use when onboarding a new project, after code review discussions about coding style, or when coding conventions need documenting. Also consider running after sessions where coding preferences were discussed or corrected (--from-conversation), or after PRs with significant review feedback (--from-pr).