audit-refactor-opportunities
Identify code smells and refactoring opportunities without fixing. Use for tech debt assessment.
Essential command-line tools and system utilities.
Identify code smells and refactoring opportunities without fixing. Use for tech debt assessment.
Python coding style guide and best practices. Use when writing Python code, reviewing Python files, or checking code style. Triggers on "python style", "python code", "파이썬 스타일", "코드 스타일".
Rust development standards including cargo test, clippy, and rustfmt. Use when working with Rust files, Cargo.toml, or Rust tests.
Use to review code implementations for quality, correctness, and best practices
Apply and validate the 7 Key Principles to code - TDD, Fail Fast, Modular, Reuse, Open Source, No Debt, Excellence. Checks code compliance and suggests improvements. Use during code review or refactoring.
Process CodeRabbit AI PR review suggestions from CODERABBIT.md in the TCC repo; triage, validate against code/specs, and implement safe, production-ready fixes.
Write clean, consistent code following established naming conventions, formatting rules, and the DRY principle across all files. Use this skill when writing any code in any file, naming variables and functions, structuring code logic, formatting code with consistent indentation, choosing descriptive names that reveal intent, keeping functions small and focused, removing dead code and unused imports, extracting common logic into reusable functions, maintaining consistent code style across the codebase, configuring linters and formatters, or refactoring code for better readability. Apply this skill universally across all coding tasks to ensure code quality, maintainability, and consistency with project standards. This skill should be active for all file types including TypeScript, JavaScript, Python, Ruby, Java, Go, and other programming languages.
Ensures Python code quality through static analysis (Ruff, Mypy) and efficient testing workflows (Pytest). Used (1) during new feature development to catch logic errors early, (2) before committing bug fixes to prevent regressions, and (3) as a final quality gate before creating a pull request.
Maintain code quality with Ruff for Python and ESLint/TypeScript for frontend. Run linters, fix issues, and ensure consistent formatting. Use when linting code, fixing style issues, or preparing to commit.
Review code changes for quality, spec compliance, and OSS readiness. Use when reviewing staged changes, PRs, or specific files for issues.
Generate configuration files for tools like ESLint, Prettier, TypeScript, and Webpack. Use when setting up project tooling or standardizing configurations.
This skill should be used when writing code in any opinionated framework's distinctive style. It applies when writing framework-based applications, creating models/controllers/views, or any framework code. Triggers on code generation, refactoring requests, code review, or when the user mentions framework conventions. Embodies the philosophy of embracing framework conventions, fighting complexity, and choosing simplicity over cleverness.
Node.js development standards including jest/vitest, eslint, and prettier. Use when working with JavaScript files, package.json, or npm/pnpm.
Reviews code for quality, security, and maintainability. Use after writing/modifying code, before commits, or when asked to review changes. Triggers on "review code", "check my changes", "code review".
Skill for validating code changes against the established baseline
Universal security checklist and fixes for ANY project type or language
Prevent and detect code quality issues in LangGraph pipelines. Use when implementing new nodes, debugging state flow issues, troubleshooting empty state keys, or before committing LangGraph code. Triggers on phrases like "validate node", "check node implementation", "trace flow", "why is state empty", "lint langgraph", "check completeness", "validate before commit", "pre-flight check", "debug state flow", "find the bug in my node".
Use when developing OpenHarmony applications to detect and fix errors systematically through lint, unit tests, compilation, automated search, and documentation lookup
Generates .stylelintrc configuration for linting CSS, SCSS, and Vue component styles. Auto-detects stylesheet type and fetches latest package versions for plugins.
Framework and stack identification with detection scripts and patterns. Use when detecting project type, analyzing framework, identifying stack, initializing projects, or when user mentions project detection, framework analysis, stack identification, or codebase analysis.