メニュー
Production-grade code review skill. Use when reviewing pull requests, auditing code quality, checking for security vulnerabilities, evaluating architecture decisions, or preparing code for production. Covers security, performance, maintainability, and correctness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Extracts full article text and metadata from web pages, then produces a clean structured summary with key claims, supporting evidence, author stance, and original source link. Use when researching a topic, fact-checking a claim, saving content for reference, or comparing coverage across multiple sources.
Guides you through building new Claude skills with a structured Q&A process. Use when you want to create a new skill from scratch, improve an existing one, or turn a repeated workflow into a reusable skill. Produces a ready-to-upload SKILL.md file.
Writes clear, appropriately-toned internal communications including project status updates, company newsletters, all-hands summaries, incident reports, FAQs, onboarding docs, and team announcements. Use when writing anything meant for a colleague, team, or company-wide audience.
Identifies and qualifies high-quality leads by analyzing your product or service, searching for target companies and contacts, and providing actionable outreach strategies. Use when building a prospect list, preparing for outbound sales, researching a target account before a call, or building an ICP (Ideal Customer Profile).
Implements and evaluates software design patterns including Clean Architecture, SOLID principles, domain-driven design, and system design best practices. Use when designing new systems, refactoring existing code, evaluating architectural trade-offs, or learning design patterns through concrete examples.
Analyzes meeting transcripts to surface behavioral patterns, extract decisions, flag unresolved issues, and identify follow-up actions. Use after any meeting where you have a transcript or detailed notes — especially useful for 1:1s, team syncs, retrospectives, and customer calls.
| name | deep-code-review |
| description | Production-grade code review skill. Use when reviewing pull requests, auditing code quality, checking for security vulnerabilities, evaluating architecture decisions, or preparing code for production. Covers security, performance, maintainability, and correctness. |
A structured, production-grade code review framework. Goes beyond "does this work" to evaluate security, performance, maintainability, and architectural soundness.
For every review, evaluate across these dimensions in order of severity:
Produce a review in this structure:
## Summary
[1-2 sentences: overall quality signal and key concerns]
## Blocking Issues
[P0 items that must be fixed before merge]
## Should Fix
[P1 items — non-blocking but expected before merge in most teams]
## Nice to Have
[P2 items — suggestions, not requirements]
## Positives
[What was done well — always include at least one]
Provide the code (paste, file, or diff) and optionally specify:
Input: "Review this Express.js middleware for auth" Approach: Focus on P0 security first (JWT validation, timing attacks, header injection), then correctness.
Input: "Review this data pipeline for performance" Approach: Focus on P1 performance (batch sizes, streaming, index usage), then correctness.
Input: "Quick pass on this utility function" Approach: Correctness and naming only. Skip architecture and test coverage sections.