Skip to content
cccskills
FreePublished on GitHub

code-standards

Reviews pull requests for bugs, error handling, code quality, and style consistency. Organizes feedback into an overview, must-fix issues with file locations, improvement suggestions, and positive notes so reviewers can distinguish urgent problems from refinements.

OriginalShow the original description

Code quality standards and style guide for reviewing pull requests

mastra-ai/mastra
See how to install

Good for

  • Finding bugs that must be fixed before merging
  • Reviewing TypeScript types and asynchronous code
  • Checking naming, imports, and leftover debug statements
  • Organizing review feedback by urgency and purpose

Files included (2)

  • SKILL.md1.8 KB
  • references/style-guide.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-prompt-quality-bar

FreeSummary

Design and audit an agent's system prompt, the instructions that guide its work. Define a concrete outcome, starting input, available tools, completion checks, fallback behavior, and final report so the prompt describes a complete run.

  • Designing the core instructions for a new agent
  • Auditing a prompt before saving it
  • Defining behavior when tools or permissions are missing
mastra-ai/mastra28.9KUpdated Oct 18, 2026

builder-smoke-test

FreeSummary

Create a dedicated test project linked to the current worktree and check Agent Builder through APIs and browser interactions. It covers agent and skill management, permissions, defaults, and related features, with selectable test sections.

  • Validate an Agent Builder feature branch before review
  • Check role-based permissions and authentication
  • Test agent and skill management through APIs and the UI
mastra-ai/mastra28.9KUpdated Oct 18, 2026

coding-agent

FreeSummary

Design instructions for agents that write, fix, review, or refactor code. Define behavior based on file access, select suitable tools, and set clear verification and completion rules for repository changes or copyable code output.

  • Designing an agent for repository bug fixes
  • Defining a pull request review agent
  • Creating a code generator without workspace access
mastra-ai/mastra28.9KUpdated Oct 18, 2026

configure-factory-rules

FreeSummary

Configure Factory board behavior and GitHub or Linear event handlers in deployment code. Adjust stage transitions, phase meanings, and tool-result handling, then check the changes with focused tests and versioned audit records.

  • Add approval requirements to board transitions
  • Change GitHub or Linear event handling
  • Define custom board phases and tool-result rules
mastra-ai/mastra28.9KUpdated Oct 18, 2026

content-writer-agent

FreeSummary

Design agents that draft blog posts, social posts, newsletters, and marketing copy. Define the audience, brand voice, length, and required output so each agent delivers a complete draft with a headline and supporting notes.

  • Build a blog writing agent with a consistent brand voice
  • Design an agent for LinkedIn product posts
  • Define delivery rules for newsletter drafts
mastra-ai/mastra28.9KUpdated Oct 18, 2026

customer-support-agent

FreeSummary

Helps build customer support agents that classify incoming messages, draft replies, and hand difficult cases to people. Defines clear rules for permitted actions, policy-based answers, privacy concerns, and verification before reporting an action as complete.

  • Designing an agent that classifies incoming support messages
  • Building a refund email agent with policy-based replies
  • Defining rules for handing sensitive cases to a person
mastra-ai/mastra28.9KUpdated Oct 18, 2026

See all skills by mastra-ai

Report a problem with this skill