code-checker

Scan C/C++ codebases for code quality issues including extra large files/functions and circular dependencies. Use when the user asks to check file sizes, find oversized functions, detect circular dependencies, analyze code complexity, find code smells, or identify maintainability issues in C/C++ code. Supports scanning individual files or entire directories with configurable thresholds.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "code-checker" with this command: npx skills add openharmonyinsight/openharmony-skills/openharmonyinsight-openharmony-skills-code-checker

C/C++ Code Checker

Analyzes C/C++ code for maintainability issues: extra large files/functions and circular dependencies between modules.

Workflow

  1. Identify scan target - If the user doesn't specify a file or directory, ask: "Which directory or file should I scan?"
  2. Determine check type - Ask or infer which checks to run:
    • File/Function size analysis
    • Circular dependency detection
    • Both (default for full analysis)
  3. Run the scan - Execute the appropriate script(s)
  4. Present findings - Show the report and summarize key issues
  5. Offer help - Ask if the user wants refactoring assistance

Size Analysis

Scan for extra large files and functions:

scripts/scan_cpp_size.py <path> [options]

Options:

  • -o, --output <file> - Write report to file
  • -f, --file-threshold <n> - Large file threshold (default: 2000 effective lines)
  • -F, --function-threshold <n> - Large function threshold (default: 50 effective lines)

Example:

scripts/scan_cpp_size.py ./src --file-threshold 1500 --function-threshold 40 -o size_report.md

Circular Dependency Detection

Detect circular dependencies between directory modules:

scripts/circular_header_check.py <path> [options]

Options:

  • -o, --output <file> - Write report to file
  • -v, --verbose - Verbose output
  • --no-gn - Skip GN build file parsing

Example:

scripts/circular_header_check.py ./src -o circular_report.md

The circular dependency checker:

  • Parses GN build files (BUILD.gn, *.gni) for include paths
  • Groups files by directory modules (handles src/ and include/ as one component)
  • Detects when module A includes files from module B, which includes A

After Finding Issues

When issues are found:

  1. Prioritize by impact - Start with the largest issues first
  2. Understand context - Read the code to understand responsibility
  3. Ask the user - "Would you like help refactoring this?"

Refactoring Guidance

Issue TypeReference
Large functionsreferences/refactoring.md
Circular dependenciesSee references/circular-deps.md

What Counts as "Large"?

CategoryDefault ThresholdRationale
Files2000 effective linesHard to navigate, understand
Functions50 effective linesBeyond cognitive fit, hard to test

Effective lines exclude blank lines, comments, and preprocessor directives.

File Extensions Scanned

.c, .cpp, .cc, .cxx, .c++, .h, .hpp, .hh, .hxx, .h++, .inl, .inc

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

ai-generated-business-code-review

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

ai-generated-ut-code-review

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

oh-pdd-code-generator

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

gitcode-pr

No summary provided by upstream source.

Repository SourceNeeds Review