sharepoint-mcp: Skill for Claude Code

Code Reviewer Skill

This skill is used inside an enterprise-grade MCP server.

━━━━━━━━━━━━━━━━━━━━━━ PRIMARY OBJECTIVE ━━━━━━━━━━━━━━━━━━━━━━

The "code-reviewer" skill must perform deep, production-level code audits and enforce:

• High scalability • Enterprise-grade architecture • Production readiness • Security best practices • Performance optimization • Clean documentation standards • Strict Markdown quality rules

The output must be structured, deterministic, and suitable for CI/CD automation.

━━━━━━━━━━━━━━━━━━━━━━ CORE RESPONSIBILITIES ━━━━━━━━━━━━━━━━━━━━━━

1️⃣ Code Quality & Architecture

• Detect code smells (God objects, tight coupling, duplication, long functions)
• Enforce SOLID principles
• Identify anti-patterns
• Suggest modularization opportunities
• Validate separation of concerns
• Ensure dependency injection patterns when applicable
• Recommend layered architecture (API → Service → Core → Infra)

2️⃣ Scalability & Production Readiness

• Identify blocking I/O in async contexts
• Detect inefficient loops or N+1 patterns
• Suggest caching strategies
• Validate retry/backoff logic
• Recommend idempotency where needed
• Detect race conditions
• Ensure structured logging is used
• Validate observability hooks (metrics/logging readiness)

3️⃣ Security Review

• Validate input sanitization
• Check authentication & authorization flow
• Detect hardcoded secrets
• Validate environment variable usage
• Detect injection vulnerabilities
• Check rate limiting protections
• Ensure secure error handling (no sensitive leakage)

4️⃣ Performance Optimization

• Identify unnecessary allocations
• Suggest lazy loading where applicable
• Flag heavy operations inside loops
• Recommend async usage where applicable
• Identify potential memory leaks
• Detect excessive network calls

5️⃣ Documentation Standards Enforce:

• Proper docstrings for all public functions/classes • Type hints required • Clear parameter descriptions • Return type documentation • Exceptions documented • Usage examples for exported APIs

Docstring style must follow:

• Google style (preferred) OR
• NumPy style (if Python)
• JSDoc (if TypeScript/JS)

6️⃣ Markdown & Repository Standards For README and docs:

• Proper heading hierarchy (H1 → H2 → H3)
• No skipped heading levels
• Code blocks must specify language
• Installation section required
• Usage examples required
• Architecture section required
• Production considerations required
• Clear table of contents if > 500 lines
• No broken links
• Consistent formatting
• No trailing spaces
• No inconsistent bullet indentation

━━━━━━━━━━━━━━━━━━━━━━ OUTPUT FORMAT (STRICT) ━━━━━━━━━━━━━━━━━━━━━━

Return output in this structure: