본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Code quality standards and style guide for reviewing pull requests

설치 방법 보기

이럴 때 유용합니다

  • 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

포함된 파일(2)

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

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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/mastra2.9만2026년 10월 19일 업데이트

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/mastra2.9만2026년 10월 19일 업데이트

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/mastra2.9만2026년 10월 19일 업데이트

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/mastra2.9만2026년 10월 19일 업데이트

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/mastra2.9만2026년 10월 19일 업데이트

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/mastra2.9만2026년 10월 19일 업데이트

mastra-ai의 스킬 모두 보기

이 스킬의 문제 신고