メニュー
Use when running static analysis on C++ source files. Triggers on "run clang-tidy", "check for warnings", "static analysis", "complexity check", or when verifying code quality.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | lint |
| description | Use when running static analysis on C++ source files. Triggers on "run clang-tidy", "check for warnings", "static analysis", "complexity check", or when verifying code quality. |
Run clang-tidy, cppcheck, and lizard. Report issues, fix what's straightforward, flag what needs planning.
imgui_effects_*.cpp functions are expected, not problemsGoal: Determine whether to use existing results or run fresh analysis
Actions:
tidy.log or run ./scripts/lint.sh fresh?"
tidy.log and proceed to Phase 3 (Present Findings)./scripts/lint.sh (optionally with thread count arg), then proceed to Phase 3STOP: Wait for user response before continuing.
Goal: Find bugs, performance issues, and style violations
Run by: scripts/lint.sh Phase 1
Severity grouping (for triage in Phase 3):
| Category | Severity | Action |
|---|---|---|
bugprone-* | High | Review, fix if real bug |
clang-analyzer-* | High | May need planning |
concurrency-* | High | Needs careful review |
performance-* | Medium | Fix if straightforward |
cert-* | Medium | Review for applicability |
readability-* | Low | Fix or suppress |
Goal: Identify complexity hotspots
Run by: scripts/lint.sh Phase 3
Thresholds:
| Metric | Warning | Error |
|---|---|---|
| CCN (cyclomatic complexity) | >15 | >20 |
| NLOC (function length) | >75 | >150 |
| Parameters | >5 | >7 |
Filter expected verbosity: Flag but don't alarm on:
imgui_effects_*.cpp functions (UI code is inherently verbose)preset.cpp serialization functionsGoal: Give user clear picture and options
Actions:
Summarize all passes:
List actionable items with file:line references
Ask user: "How would you like to proceed?"
STOP: Do not fix without user consent.
Goal: Address selected issues
Skip if: User chose informational only
Actions:
For clang-tidy fixes:
// NOLINT(check-name) - reason for intentional patternsFor complexity issues (rare - most are UI verbosity):
Verify fixes by running ./scripts/lint.sh again
Goal: Report what was done
Actions:
Suppress clang-tidy warnings only when:
Always document:
// NOLINT(readability-named-parameter) - raylib callback signature
void AudioCallback(void *buffer, unsigned int frames) { ... }
| Thought | Reality |
|---|---|
| "I'll fix all these warnings" | User decides. Present and ask. |
| "This 200-line UI function needs refactoring" | It's ImGui. That's normal. |
| "I'll suppress this to make it pass" | Suppressions need justification. |
| "The complexity is too high" | CCN matters more than NLOC for UI code. |
scripts/lint.sh (runs all three tools, saves to tidy.log).clang-tidy (project root)pip install lizardUse when adding a new transform effect, creating a post-process shader, or planning effect implementation. Provides the complete checklist of files and commonly-missed steps.
Use when exploring a vague idea, finding inspiration, or researching a technique before planning. Triggers on "I want to add...", "what if...", "research", "look up", or when uncertain about what to build.
Use when creating a git commit for staged or unstaged changes. Triggers on "commit this", "save my changes", or when implementation work completes and needs version control.
Use when creating a tagged release with changelog. Triggers on "release", "tag a release", "cut a release", or when ready to publish a new version.
Use when reviewing an implemented feature against its plan document. Triggers after implementation completes, on "review this", or when checking if code matches specification.
Use when planning a new feature before implementation. Triggers on "plan", "design", "architect", or when describing a feature to build.