All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 14,947
- 623
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 217–240 of 14,947 skills
- Feat ReviewUse when the user wants a code review of an explicit range or set of files — correctness, security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and rule citations — 'revisar os últimos commits', 'code review da feature X', 'review base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.Votes: 0GitHub stars: 3
- Component RefactoringRefactor high-complexity React components. Use when complexity metrics are high or to split monolithic UI.Votes: 0GitHub stars: 2
- Component Patterns 3WHAT: React Native component patterns with variant-based architecture and repository pattern. WHEN: creating components, implementing variants, separating data logic from UI. KEYWORDS: component, variant, discriminated union, repository, FlatList, useCallback, memo, JSX, props.Votes: 0GitHub stars: 2
- Component BuilderBuilds production-ready Keboola Python components with best practices and architectural patterns. Use when creating new extractors/writers/applications, implementing incremental loads, designing configuration schemas, adding API client separation, following self-documenting workflow patterns, or setting up components with cookiecutter templates and Ruff code quality.Votes: 0GitHub stars: 2
- ComplexityAnalyze code complexity and find refactor targets using radon/gocycloVotes: 0GitHub stars: 2
- Complexity ManagementMaintain and improve code quality using PHPInsights without decreasing quality thresholds. Use when PHPInsights fails, cyclomatic complexity is too high, code quality drops, or when refactoring for better maintainability. Always maintains 93% complexity for src/ and 95% for tests/, plus 100% quality/architecture/style scores.Votes: 0GitHub stars: 2
- CommunicationWriting and collaboration standards for PR reviews, PR descriptions, and ticket updates. Use when writing messages that other humans will read (PR review comments, PR bodies, JIRA ticket bodies/comments).Votes: 0GitHub stars: 2
- Commitlint 1When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.Votes: 0GitHub stars: 2
- Commit WorkflowFluxo completo de Git: branches, commits, pull requests e code reviewVotes: 0GitHub stars: 2
- Commit PushThis skill should be used when the user asks to "commit and push", "push my changes", or wants to commit, push, and respond to PR comments.Votes: 0GitHub stars: 2
- Commit Push Pr 3Git 提交推送流程。触发词:提交、推送、PR、commit。Votes: 0GitHub stars: 2
- Commit MilestonesAutomatically commit changes when reaching major milestonesVotes: 0GitHub stars: 2
- Commit MessagesGenerate conventional commit messages based on staged changes. Use when writing commit messages, understanding conventional commit format, or ensuring consistent commit history.Votes: 0GitHub stars: 2
- Commit Message GuidelinesProvides guidelines for creating conventional commit messages, ensuring they adhere to a specific format and are concise.Votes: 0GitHub stars: 2
- Commit Message 9Generate commit messages following conventional commits with scope detectionVotes: 0GitHub stars: 2
- Commit Message 4Generates clear commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or when the user asks to create a commit.Votes: 0GitHub stars: 2
- Commit Message 3Write git one-line commit messages.Votes: 0GitHub stars: 2
- Commit Helper 5Generate conventional commit messages from staged changes. Runs autonomously using Haiku model. Use after completing TDD cycles, after refactoring sessions, or when ready to commit.Votes: 0GitHub stars: 2
- Commit ChangesCreate clear, informative, and well-structured Git commit messages following best practices and conventional commit standards.Votes: 0GitHub stars: 2
- Commit 67Create git commits in spaces/[project]/ with conventional message format. Use for saving progress with quality checks and proper commit messages.Votes: 0GitHub stars: 2
- Commit 61Enforce disciplined, file-by-file Git commits using strict verbs, scoped brackets, and short messages. Use when staging, refactoring, fixing, or cleaning code. Especially useful for refactors, audits, and review-friendly history.Votes: 0GitHub stars: 2
- Commit 55Create a well-formatted git commit following best practicesVotes: 0GitHub stars: 2
- Commit 52This skill should be used when the user says "commit changes", "commit this", "commit my work", "save to git", "save my changes", "push this", "push my work", "create a commit", or wants to save their work to version control. Handles the full git workflow including staging, committing, and pushing.Votes: 0GitHub stars: 2
- Commit 5Complete pre-commit workflow - run quality checks (format, lint, type, test) and validate/create conventional commit messagesVotes: 0GitHub stars: 2