code-review-checklist
Code review guidelines covering code quality, security, and best practices.
Discover data ai automation tools skills, compare source repositories and read the instructions for each workflow.
Code review guidelines covering code quality, security, and best practices.
Reviews code for construction management applications with focus on CSI data integrity, BIM workflows, and domain-specific correctness. Use when reviewing changes to calculator logic, database schemas, or const...
Runs automated verification after code changes in Next.js + TS projects. Invoked by prompt-classifier in IMPLEMENT/EDIT sequences (after write/edit). Executes lint, scoped typecheck, tests, custom assertions; r...
Reviews code for security vulnerabilities. Use when security concerns are detected or before deploying critical changes.
This skill should be used when the user asks to "review code", "review this PR", "code review", "audit this code", or mentions reviewing pull requests, security checks, or code quality. Covers security (OWASP),...
Systematic code cleanup and refactoring agent that identifies and fixes code quality issues without changing functionality. Focuses on: - Dead code removal - Import organization - Type improvements - Consistent...
Review code changes for bugs, logic errors, regressions, and missing tests. Use when the user asks for a code review, review of uncommitted files, or review of specific diffs/files/PR changes. Default to uncomm...
Senior frontend code review for Vue/TypeScript. Use when reviewing PRs, checking code quality, or validating against project conventions.
[slop] [debug] [unused] [duplicates] [all] - Cleans up code in the current branch. Removes AI artifacts, debug statements, unused code, and duplicates. Use when preparing for PR or cleaning up after AI-assisted...
Create custom Semgrep rules for detecting bug patterns and security vulnerabilities. This skill should be used when the user explicitly asks to "create a Semgrep rule", "write a Semgrep rule", "make a Semgrep r...
Builds and refactors code safely; prefers small diffs, clear validation steps, and testable outcomes.
Generates or augments minimal Vitest tests for changed/new code in Next.js + TypeScript projects. Invoked by prompt-classifier on TEST or chained from other flows. Focuses on happy path + key edges. Chains veri...
Complete Git workflow from conventional commits to pre-completion verification. Use for all Git operations including commits, branches, and releases.
Addresses PR review comments systematically. Use when fixing review feedback, responding to code review threads, or processing PR comments.
Automates the end-to-end Git workflow from committing to feature branch to merging via the GitHub CLI.
GitHub PR 제목과 본문을 자동 생성하고 코드리뷰까지 수행. "do it PR", "PR 작성", "풀리퀘스트" 키워드로 자동 활성화
Standardized patterns for Git branching, worktrees, and lifecycle management.
PR workflow, release notes, build management, and GitHub conventions. Use when creating PRs, writing commit messages, or preparing releases.
Project structure and coding conventions for RawDrive. Use when creating new files, organizing code, or understanding the codebase layout. CRITICAL for preventing random file creation.
The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review...
Manage CodeCommit PRs (create/list/view)
Manages safe git branching, conventional commits, and push flow for Next.js + TS projects. Invoked by prompt-classifier at end of IMPLEMENT/EDIT sequences after verification-guardian passes. Ensures work happen...
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.