Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

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

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. Logic Review: Check for bugs and edge cases
  2. Security Scan: Look for vulnerabilities (injection, auth issues, etc.)
  3. Performance Check: Identify bottlenecks and inefficiencies
  4. 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:

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

Example 2: Directory Review

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

Expected Behavior:

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

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

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace443Updated Oct 23, 2026

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.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace443Updated Oct 23, 2026

Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace443Updated Oct 23, 2026

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: web automation, data extraction, testing, agent browsing, research. Triggers: browser, web automation, scrape, navigate, click, fill form, screenshot, browse web, playwright, headless browser, web agent, surf internet, record video

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace443Updated Oct 23, 2026

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace443Updated Oct 23, 2026

Run AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter, and many more. Use when running AI apps, generating images/videos, calling LLMs, web search, or automating Twitter. Triggers: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace443Updated Oct 23, 2026

See all skills by aiskillstore

Report a problem with this skill