code-quality-guard_skill

Overview

This skill provides a professional pre-deployment code review and quality enforcement pipeline that prevents simple issues from reaching production. It automatically checks imports, verifies that JSX/HTML tags are balanced, audits environment requirements, and scans logs for debug artifacts or exposed secrets. Use it as a build hook to block unsafe or incomplete builds and speed up safe releases. The goal is fewer runtime failures and clearer feedback for developers before a build is declared live.

How this skill works

Code-quality-guard analyzes source files and the project environment before the build completes. It performs an import sweep to ensure every referenced component is declared and flags unused or missing imports. It parses templates to confirm tags are balanced and checks environment configuration for required variables and ports. The tool also inspects logs and source for debug prints, hard-coded secrets, and common patterns that indicate sensitive data exposure.

When to use it

• As a pre-build or pre-deploy hook in CI pipelines to catch ReferenceErrors early.
• Before releasing a version to staging or production to enforce consistency.
• When onboarding new contributors to ensure they follow project import and tagging conventions.
• During automated archive or backup processes to validate code health before storage.
• When integrating third-party code to ensure imports and environment requirements match project expectations.

Best practices

• Run the guard in CI for every pull request and block merges with high-risk findings.
• Treat missing imports and unbalanced tags as build blockers to avoid runtime crashes.
• Maintain a minimal, documented set of required environment variables so audits are deterministic.
• Combine static checks with targeted unit tests for logic validation beyond syntactic checks.
• Review flagged log entries and secrets immediately; rotate exposed keys and re-run checks.

Example use cases

• Catch a missing React import that would cause a ReferenceError in production UI.
• Detect unclosed JSX tags introduced during a refactor before deploying frontend code.
• Verify that required PORT and DATABASE_URL environment variables are present for a deploy.
• Scan for leftover console.log or print statements that should not appear in production logs.
• Prevent a build that contains hard-coded API keys from being released to public archives.