本文へ移動
cccskills
無料GitHub で公開

code-standards

Code quality standards and style guide for reviewing pull requests

インストール方法を見る

含まれるファイル(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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Universal quality bar and final audit rubric for any agent system prompt. Activate this whenever you are unsure which archetype skill applies, or as a final review pass before writing the system prompt. It defines the required run contract, completion criteria, fallback paths, response format, and anti-patterns every produced agent prompt must satisfy.

日本語の概要は準備中です。原文の説明を表示しています。

mastra-ai/mastra2.9万2026年10月12日 更新

Smoke test the Agent Builder feature branch end-to-end against a hermetic project scaffolded by the skill (linked to the current worktree). Covers workspace reconciliation, stored agents/skills CRUD, ownership, visibility, stars, registry/library Copy flow, picker allowlists, model policy, RBAC role gating, role impersonation UI, builder defaults, infrastructure diagnostics, channels, and Studio + Agent Builder UI. Trigger when validating the agent-builder feature branch, PRs that touch packages/server, packages/playground, packages/playground-ui agent-builder routes, or builder EE code paths.

日本語の概要は準備中です。原文の説明を表示しています。

mastra-ai/mastra2.9万2026年10月12日 更新

Authoring playbook for building agents that write, edit, review, or refactor code. Use this when the user asks for an agent that writes scripts, generates code, reviews pull requests, refactors a codebase, fixes bugs, implements features, writes tests, or works with programming languages such as Python, TypeScript, JavaScript, Go, Rust, SQL, or shell.

日本語の概要は準備中です。原文の説明を表示しています。

mastra-ai/mastra2.9万2026年10月12日 更新

Configure board-owned lifecycle, policy, phase-semantics, and tool-result rules, plus integration event rules

日本語の概要は準備中です。原文の説明を表示しています。

mastra-ai/mastra2.9万2026年10月12日 更新

Authoring playbook for building agents that draft written content — blog posts, marketing copy, social media posts, newsletters, product descriptions, landing pages, or ad copy. Use this when the user wants an agent that writes, drafts, or rewrites text for publication or marketing.

日本語の概要は準備中です。原文の説明を表示しています。

mastra-ai/mastra2.9万2026年10月12日 更新

Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues. Use this when the user wants an agent that handles inbound customer questions, drafts replies, escalates hard cases, summarizes tickets, or follows a support playbook.

日本語の概要は準備中です。原文の説明を表示しています。

mastra-ai/mastra2.9万2026年10月12日 更新

mastra-ai のスキルをすべて見る

このスキルの問題を報告する