reviewing-code

Detect languages in diffs and run linters, security checks, and coverage analysis.

35|5|Updated Jul 5, 2025
One-click install
npx skills add https://github.com/alexei-led/cc-thingz --skill reviewing-code-alexei-led
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/alexei-led/cc-thingz/tree/main/plugins/dev-workflow/skills-codex/reviewing-code
Command: npx skills add https://github.com/alexei-led/cc-thingz --skill reviewing-code-alexei-led

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sequential code review for security, quality, and architecture. Detects languages in the diff, runs linters and static checks, reviews for OWASP security issues, quality patterns, and test coverage gaps, then reports findings grouped by severity.

Core Features & Use Cases

  • Sequential language-aware checks: detects changed languages (Go, Python, TypeScript, web) and runs appropriate linters and static checks.
  • Security and quality analytics: identifies OWASP risks, quality patterns, and potential coverage gaps; aggregates results by severity.
  • Use Case: In a PR with mixed Go and Python changes, surface critical issues and guide remediation before merge.

Quick Start

Use the reviewing-code skill to scan the latest diff and start a guided, sequential review across detected languages.

Frequently Asked Questions about reviewing-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate security code reviews for a multi-language pull request?

Automate security code reviews by detecting changed languages in the diff and running language-specific linters, static checks, and test-coverage analysis. This process identifies OWASP risks and quality issues, aggregating structured remediation guidance by severity.

What is the best way to run language-aware static analysis and lint checks on a mixed Go and Python diff?

Run language-aware static analysis by detecting languages in the diff and executing appropriate linters for each. It sequentially scans mixed Go, Python, TypeScript, and web codebases to surface critical issues and guide remediation before merge.

Can I identify OWASP security risks and test coverage gaps automatically in my code review workflow?

Yes, you can identify OWASP security risks and test coverage gaps automatically. The workflow reviews changed files for security vulnerabilities and quality patterns, then aggregates all findings into a structured report grouped by severity.

Does this automated code review approach work without external dependencies?

Yes, this automated code review approach works without external dependencies. It orchestrates language detection, linter execution, and static analysis internally to output structured remediation guidance.

How are code review findings grouped and reported for remediation?

Code review findings are grouped and reported by severity. The workflow aggregates security vulnerabilities, quality patterns, and test coverage gaps into structured guidance to help developers prioritize remediation.

When do I need language-aware code review for security and architecture?

You need language-aware code review when merging pull requests with mixed Go, Python, or TypeScript changes. It detects languages in the diff, runs targeted static checks, and surfaces critical security and architecture issues before merge.