code-qc

What This Skill Does

The code-qc skill acts as an intelligent, automated quality assurance engineer for your software projects. Rather than relying on simple linting, it executes an 8-phase audit that combines industry-standard static analysis (ruff, eslint, gdlint) with semantic logic checks and dynamic smoke test generation. It provides a standardized PASS/WARN/FAIL verdict, making it an essential tool for maintaining code health, ensuring type safety, and monitoring technical debt over time. By utilizing a configurable .qc-config.yaml file, it adapts to specific language requirements and team standards, allowing for project-specific thresholds and exclusions.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/isonaei/code-qc

Ensure your project contains a .qc-config.yaml in the root directory if you wish to override the default sensitivity or exclusion rules.

Use Cases

• Automated PR Reviews: Run the audit in --changed-only mode during CI/CD workflows to catch regressions before merging.
• Legacy Codebase Audits: Perform a full 8-phase audit to establish a baseline of test coverage, documentation quality, and linting errors for a project you are inheriting.
• Trend Analysis: Periodically execute the skill to compare QC results over time, tracking whether code quality is improving or degrading as features are added.
• Sanity Checks: Use the --quick flag for a rapid verification of imports, syntax, and linting status during active development iterations.

Example Prompts

1. "Run a full quality control audit on this project and tell me if it passes our standard criteria."
2. "Perform a quick sanity check and show me the report for the latest changes in the current branch."
3. "Compare our current codebase quality against the baseline from last week—what has improved or regressed?"

Tips & Limitations

• Configuration: Always define your thresholds in .qc-config.yaml to match your team’s definition of 'clean' code; otherwise, the tool defaults to strict modes.
• Language Support: While the tool is optimized for Python, TypeScript, and GDScript, it can handle general projects; ensure your project-specific testing tools (like pytest or npm) are configured correctly in your environment.
• Safety: Because this skill executes testing scripts and static analysis tools, ensure that your environment is properly sandboxed if you are auditing untrusted codebases.