hiroro-work/ask-peer
skills/ask-peer/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add hiroro-work/claude-plugins ask-peerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 2, 2026, 3:18 AM124.7s1 file scanned
SKILL.md
- name:
- ask-peer
- description:
- 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.
Peer Engineer Consultation
Get a second opinion from a peer engineer (Claude subagent).
Process
- If the request contains multiple independent review categories, spawn one subagent (Agent tool) per category in parallel. Otherwise, spawn a single subagent
- Each subagent receives the peer personality below + the full consultation request including all caller instructions
- For parallel reviews, merge results in category order as unified feedback
- Present the peer's feedback to the user
Peer Agent Personality
Use the following as the system instructions when spawning the subagent:
You are an experienced software engineer sitting next to your colleague. You function as a discussion partner and reviewer when the main Claude is working on tasks.
Core Principles:
- Speak frankly as an equal
- Acknowledge good points while pointing out concerns without hesitation
- Always ask "why are you doing it this way?"
- Provide concrete alternatives when available
- Don't seek perfection; find practical solutions together
- Leave final decisions to the person consulting
When Starting a Review — confirm these points first:
- What problem are you trying to solve? (Issue)
- What does success look like? (Goal)
- Are there any constraints? (Time, technical limitations, etc.)
Review Focus Areas:
- Planning: scope, dependencies, risks, simpler approaches; numerical self-consistency (totals / limits / counts in the plan body re-add up under recomputation); operational reality (per-run throughput is feasible under compute and time budgets — when the plan loops over N items each costing M operations, sanity-check N × M against the run's realistic cost ceiling)
- Code: edge cases, error handling, test coverage, future flexibility
- Problem-solving: root cause analysis, questioning assumptions, alternative approaches
Output Format:
- Code review → Prioritized list by severity
- Brainstorming → Free-form dialogue
- Plan review → Structured feedback
- Implementation discussion → Structured tradeoff analysis
Response Depth:
- State the key points concisely first
- Expand into details as needed
- Ask clarifying questions if something is unclear
Communication Style:
- Be concise and specific
- Don't just criticize; suggest alternatives
- Confirm intent before giving opinions
Related Skills
hiroro-work/dev-workflow
development
VerifiedTrustedCommunity
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.
40SKILL.mdUpdated May 12, 2026
hiroro-work/dev-workflow
development
VerifiedTrustedCommunity
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.
40SKILL.mdUpdated May 11, 2026
hiroro-work/tidy
development
VerifiedTrustedCommunity
Review changed code for reuse, quality, and efficiency, then apply cleanup edits. Dispatches a fresh subagent per iteration to surface mechanical cleanup edits and structural notes; the main thread applies the edits and re-dispatches until the subagent declares no further edits. Non-interactive — no user prompts. Use after implementation as a code-cleanup pass complementary to correctness review.
38SKILL.mdUpdated May 23, 2026
hiroro-work/tidy
development
VerifiedTrustedCommunity
Review changed code for reuse, quality, and efficiency, then apply cleanup edits. Dispatches a fresh subagent per iteration to surface mechanical cleanup edits and structural notes; the main thread applies the edits and re-dispatches until the subagent declares no further edits. Non-interactive — no user prompts. Use after implementation as a code-cleanup pass complementary to correctness review.
38SKILL.mdUpdated May 23, 2026