code-standards
Code quality standards and style guide for reviewing pull requests
Best use case
code-standards is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Code quality standards and style guide for reviewing pull requests
Teams using code-standards should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/code-standards/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How code-standards Compares
| Feature / Agent | code-standards | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Code quality standards and style guide for reviewing pull requests
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Code Standards Review When reviewing code, follow this structured process: ## Step 1: Critical Issues Check for issues that MUST be fixed before merging: - Logic bugs and incorrect behavior - Missing error handling for failure cases - Race conditions or concurrency issues - Unhandled edge cases (null, undefined, empty arrays, boundary values) - Breaking API changes without migration path ## Step 2: Code Quality Evaluate overall code quality: - Functions should do one thing and be reasonably sized (< 50 lines preferred) - Avoid code duplication — look for repeated patterns that should be abstracted - Use descriptive, meaningful names for variables, functions, and types - Prefer explicit types over `any` in TypeScript - Ensure proper use of async/await (no floating promises, proper error propagation) ## Step 3: Style Guide Conformance Check against the style guide in `references/style-guide.md`: - Naming conventions - Code organization and import ordering - Comment quality (explain "why", not "what") ## Step 4: Linting Flags Flag these patterns: - `var` usage (should be `const` or `let`) - Leftover `console.log` or `debugger` statements - Commented-out code blocks - Magic numbers without named constants - `TODO` or `FIXME` comments without issue references ## Output Format Structure your feedback as: 1. **Summary**: 1-2 sentence overview of the changes and overall quality 2. **Critical Issues**: Must-fix problems with file path and line numbers 3. **Suggestions**: Improvements that would make the code better 4. **Positive Notes**: Good patterns and decisions worth acknowledging
Related Skills
security-review
Security-focused code review checklist for identifying vulnerabilities
performance-review
Performance-focused code review for identifying bottlenecks and optimization opportunities
customer-support
Guidelines for handling customer support interactions. Use when responding to user inquiries, troubleshooting issues, or escalating problems.
code-review
Provides structured code review guidelines for TypeScript projects. Use when reviewing pull requests, analyzing code quality, or suggesting improvements.
api-design
Guidelines for designing RESTful APIs and TypeScript interfaces. Use when designing new endpoints, reviewing API contracts, or structuring data models.
brand-guidelines
Applies Mastra's brand colors, typography, and writing style to documentation, code examples, or artifacts. Use when brand colors, style guidelines, visual formatting, or company design standards apply.
tailwind-best-practices
Tailwind CSS styling guidelines for Mastra Playground UI. This skill should be used when writing, reviewing, or refactoring styling code in packages/playground-ui and packages/playground to ensure design system consistency. Triggers on tasks involving Tailwind classes, component styling, or design tokens.
smoke-test
Create a Mastra project using create-mastra and smoke test the studio in Chrome
react-best-practices
React performance optimization guidelines from Mastra Engineering. This skill should be used when writing, reviewing, or refactoring React code to ensure optimal performance patterns. Triggers on tasks involving React components, data fetching, bundle optimization, or performance improvements.
ralph-plan
Interactive planning assistant that helps create focused, well-structured ralph-loop commands through collaborative conversation
mastra-docs
Documentation guidelines for Mastra. This skill should be used when writing or editing documentation for Mastra. Triggers on tasks involving documentation creation or updates.
e2e-tests-studio
REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.