code-review
Review code changes for quality, spec compliance, and OSS readiness. Use when reviewing staged changes, PRs, or specific files for issues.
Découvrez les skills documentation automation tools, comparez leurs dépôts et consultez leurs instructions.
Review code changes for quality, spec compliance, and OSS readiness. Use when reviewing staged changes, PRs, or specific files for issues.
Review specification and developer documents for compliance with project guidelines. Use when checking docs-spec/ and docs-site/docs/ for ambiguous expressions or missing required sections.
Instructions for building and installing VS Code extensions in this project.
Instructions for adding to bash auto completions in the AutomateLinux project.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...
Find dead code, duplications, complexity issues, and refactoring opportunities. Use when cleaning up code, removing unused exports, simplifying complex functions, or during tech debt sprints.
Perform OWASP Top 10 security audit, check auth/authz guards, find injection vulnerabilities, and identify data exposure. Use when reviewing security-sensitive code, before merging auth changes, or when asked t...
Audit npm dependencies for security vulnerabilities, outdated packages, unused deps, license compliance, and bundle impact. Use regularly for security hygiene, before major releases, or when bundle size grows u...
GitHubのプルリクエスト(PR)作成を自動化。変更のコミット、プッシュ、PR作成を実行。「PRを作って」「プルリクエスト作成」「pull request」などの依頼で起動。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...
Use for any git operations: fixing PRs, creating commits, creating branches, pushing changes. Handles proper branch management, commit conventions, and stacked PRs.
You are planning to simplify and improve the location of a file. The goal is to ensure the file is in the correct place within the project folder structure.
You are an expert user of GitHub. You interact with GitHub repositories, issues, projects and prs.
Versatile Codex MCP integration for code review, technical research, documentation generation, and custom technical queries. Automatically constructs optimized prompts and gathers project context.
Refactors "code slob" (technical debt) into clean, idiomatic Python code, using rigorous verification to ensure zero regressions. Use when the user asks to "refactor", "clean up", or "optimize" a file.
Sync design docs with codebase state. Use when verifying documentation accuracy, after code changes, or when last-synced is stale.
Automatically selects appropriate review perspectives based on file type and characteristics. Use when initiating code review to determine which review-points files should be applied.
Code formatting with Prettier for TypeScript/NestJS projects. Trigger: After editing/creating files, before committing code, ensuring code style consistency.
Git commit management following Conventional Commits specification for Aurora projects. Trigger: When creating commits, analyzing git history, or reviewing commit messages.
Provides structured information about the Aurora/NestJS project folder hierarchy, explaining the purpose and responsibility of each directory and key files. Trigger: When user asks about project structure, fold...
Writing and modifying Claude Code hooks. Auto-applies when editing files in hooks/, creating new hooks, or debugging hook behavior.
GitHub Actions and CI/CD best practices for automated testing, building, and deployment.
Python development best practices for modern Python projects. Activated when working with Python files, pyproject.toml, or discussing Python patterns, testing, linting, type hints.
Best practices for using just command runner and task automation in development workflows.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.