無料GitHub で公開

code-review

Use this skill when user asks to "review code", "check for issues", "analyze code quality", "find bugs", or wants feedback on code implementation.

aiskillstore/marketplace

インストール方法を見る

含まれるファイル（2）

SKILL.md2.7 KB
skill-report.json9.3 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Code Review

Perform thorough code review analyzing quality, potential bugs, security issues, and suggesting improvements.

Parameters

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string",
      "description": "File path, directory, or glob pattern to review"
    },
    "focus": {
      "type": "string",
      "enum": ["general", "security", "performance", "maintainability"],
      "description": "Primary focus area",
      "default": "general"
    }
  },
  "required": ["target"]
}

When to Use

User asks to "review" or "check" code
User wants to find bugs or issues
User asks about code quality
User wants security analysis
User asks for improvement suggestions

Methodology

Phase 1: Context Gathering

Read the target files
Understand the codebase structure
Identify the programming language and framework
Check for related tests and documentation

Phase 2: Analysis

Logic Review: Check for bugs and edge cases
Security Scan: Look for vulnerabilities (injection, auth issues, etc.)
Performance Check: Identify bottlenecks and inefficiencies
Style Review: Check consistency and best practices

Phase 3: Prioritization

Categorize issues by severity (Critical, High, Medium, Low)
Focus on actionable feedback
Provide concrete examples

Phase 4: Output

Provide structured review with:

Summary of findings
Issues list with severity and line numbers
Specific improvement suggestions
Code examples where helpful

Guidelines

Be constructive, not just critical
Provide specific line references
Explain WHY something is an issue
Suggest concrete fixes, not just problems
Acknowledge good patterns when found
Consider the project's existing style

Examples

Example 1: File Review

User Input: "Review src/auth.ts for security issues"

Expected Behavior:

Read the file and understand authentication flow
Check for common security issues (SQL injection, XSS, weak crypto)
Verify input validation and sanitization
Check for proper error handling
Provide prioritized list of findings with fixes

Example 2: Directory Review

User Input: "帮我 review 一下 src/utils/ 目录的代码质量"

Expected Behavior:

列出并读取目录中的所有文件
分析代码结构、命名、错误处理
检查是否有重复代码或可抽象的模式
用中文输出详细的 review 报告
按严重程度排序问题列表

レビュー

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

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

acquisition-policy-workflow

無料

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing prior policy analysis; or producing an Acquisition Policy Impact Brief. Use published federal sources and supplied policy documents without making legal or procurement-specific applicability determinations. Do not use for clause selection, market research execution, opportunities, pricing, grants, or cooperative agreements.

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