- Home
- Skills
- Georgekhananaev
- Claude Skills Vault
- Code Quality
code-quality_skill
- Python
9
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill georgekhananaev/claude-skills-vault --skill code-quality- SKILL.md8.5 KB
Overview
This skill provides production-grade code quality standards and review for TypeScript, Python, Go, and Rust. It enforces type safety, security, performance, and maintainability through checklist-driven reviews, language-specific rules, and CI-friendly enforcement. Use it when writing, reviewing, or refactoring code to keep commits and PRs production-ready.
How this skill works
The skill inspects code against a core ruleset (type safety, security, complexity, error handling) and language-specific standards (TS, Python, Go, Rust). It produces a categorized review using severity levels (Critical, Error, Warning, Style) and a structured report with file locations, impact, and precise fixes. It also includes CI configs, lint presets, and a PEP 8 deep-dive for Python.
When to use it
- When authoring new features or refactoring across TS/Python/Go/Rust
- During PR reviews to block critical issues and enforce standards
- Setting up linting, pre-commit, and CI enforcement for a repo
- Security or performance audits and dependency scanning
- When you need a PEP 8–focused review for Python code
Best practices
- Enable strict typing in TypeScript and mypy strict in Python; avoid implicit any or untyped functions
- Treat Critical and Error severities as merge blockers; auto-fix Style issues in CI
- Keep functions small (ideally <30 lines) and limit cyclomatic complexity to 10
- Use parameterized queries, avoid hardcoded secrets, and run SCA and gitleaks scans
- Adopt progressive enforcement: start with warnings, tighten on new/touched files, then full enforcement
Example use cases
- Automated PR review that flags type violations, security vulnerabilities, and complexity regressions
- Repository setup: add ESLint/tsconfig, Ruff+mypy, golangci-lint, and clippy with provided configs
- Refactor session: run the checklist to find uncaught errors, ignored returns, or unwraps in production code
- Python style audit: PEP 8 deep-dive with concrete fixes, typing recommendations, and auto-fix scripts
- CI gate: block merges on Errors/Criticals and run incremental checks for faster feedback
FAQ
TypeScript, Python, Go, and Rust with language-specific linters and rulesets.
How are issues prioritized?
Issues use four severities: Critical (block), Error (block), Warning (must address), Style (auto-fixable).
Can I run checks incrementally in a monorepo?
Yes. Provided scripts support changed-file checking and progressive enforcement modes to speed feedback.