| name | cpp-core-guidelines-review |
| description | Parallel C++ Core Guidelines code review using multiple specialized sub-agents. Use when reviewing C++ code, modules, or files against C++ Core Guidelines to identify violations. Each sub-agent reviews against a specific guideline section (Functions, Classes, Resource Management, etc.) and outputs findings to separate markdown files in the review/ directory, followed by a consolidated summary. |
C++ Core Guidelines Review
Overview
Review C++ code against the C++ Core Guidelines by launching parallel sub-agents, each analyzing code against a specific guideline section. This skill ensures comprehensive coverage while maintaining high confidence in violation identification.
Workflow
Step 1: Understand Scope Clarification
Before launching any sub-agents, clarify the review scope with the user:
- Target files/directories: Which C++ source files or directories to review?
- File patterns: What file extensions should be included? (e.g.,
.cpp, .h, .hpp)
- Exclusions: Any files or directories to exclude?
Important: Do not proceed until the scope is clearly defined and unambiguous.
Step 2: Launch Parallel Sub-Agents
CRITICAL REQUIREMENTS:
- You MUST launch one sub-agent for EVERY file in
references/Content/. Do not skip any files. Each guideline section requires its own dedicated sub-agent.
- Use the guideline-section-reviewer agent in
agents/guideline-section-reviewer.md from this plugin for each sub-agent.
Parallel launch strategy: To maximize performance, launch all sub-agents in parallel by sending multiple Task tool calls in a single response message. The Task tool documentation explicitly states: "When the user specifies that they want you to run agents 'in parallel', you MUST send a single message with multiple Task tool use content blocks."
