Total 53,920 skills, Code Quality has 2431 skills
Showing 12 of 2431 skills
Use when writing or reviewing any TypeScript code. Covers discriminated unions, branded types, Zod at boundaries, const arrays over enums, and safe access patterns.
Supports automatic generation/optimization/fixation/checking of index files to ensure all index files (index.ts / index.js) comply with the barrel export specification. Core principle: All index files must follow the barrel export specification.
When dealing with python code, these guidelines must always be followed.
Run Codex CLI /review via tmux to review uncommitted changes. Launches Codex in isolated tmux session, sends /review command, selects option 2, captures output. Use when you want a second opinion on uncommitted code changes.
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Biome 2.x linting and formatting patterns. Use when configuring code quality tools, setting up linting rules, formatting code, or integrating with CI/CD. Covers migration from ESLint/Prettier.
Request code review and route results to a tmux pane. Default flow commits first; optional opt-in flow can target an existing commit without commit/push.
FaasJS best practices - file conventions, defineFunc, database(knex).
Guides file and folder organization using fractal tree structure: self-similar directories, encapsulation, shared/ folders, mini-library pattern, and kebab-case naming. Use when creating, moving, or renaming files, extracting modules into subdirectories, deciding where shared code belongs, or checking import boundaries.
Guidance on Python code style optimization and Pythonic idioms; Based on the complete content of *One Python Craftsman* and the "Friendly Python" concept, covering variable naming, control flow, data types, container types, function design, exception handling, decorators, file operations, and SOLID principles; Providing user-friendly and maintainer-friendly design patterns, review checklists, and over 140 practical templates
This skill is used when users request phrases such as 'handle PR review issues', 'fix review items', 'resolve PR feedback', 'process review issues one by one', 'complete review tasks', 'run pr review resolver', 'resolve PR review', 'address review comments', 'fix review findings', or 'handle code review'. It reads the review comments of the PR associated with the current branch, discusses each unresolved issue with the user one by one, lets the user decide on the handling approach, and executes fixes in parallel as background subtasks.
Senior engineering analyst for code review, plan review, and automation review. Four-lens review covering architecture, code quality, reliability, and performance, each scored 1-10. Delivers APPROVE, REVISE, or REJECT verdicts. Use when you need a code review, plan review, quality check, or want to verify work before shipping. Part of the architect-system loop. Reads from system/blueprints/ and source code. Outputs to system/reviews/.