search-analyze-report-template

djankies's avatarfrom djankies

[REPLACE] Search for patterns, analyze findings, generate structured reports. Use when [REPLACE with specific triggers].

⭐0stars🔀0forks📁View on GitHub🕐Updated Nov 25, 2025
[Code Review]

When & Why to Use This Skill

This Claude skill provides a systematic Search-Analyze-Report workflow designed to examine codebases for specific patterns, categorize findings by severity, and generate structured reports with actionable recommendations. It streamlines the process of code auditing, technical debt assessment, and architectural analysis by automating the discovery and documentation of complex code patterns.

Use Cases

  • Security Vulnerability Scanning: Automatically search for common security flaws like SQL injection or XSS patterns across the codebase and generate a prioritized risk report with remediation steps.
  • Technical Debt Audit: Identify deprecated API usage, legacy code patterns, or 'TODO' markers across a large repository to plan and prioritize refactoring efforts.
  • Architectural Compliance: Verify that the codebase adheres to specific design patterns or naming conventions, providing a detailed gap analysis and recommendations for alignment.
  • Dependency and Impact Analysis: Search for specific library imports or component usages to understand the impact of potential changes or upgrades across multiple modules.
namesearch-analyze-report-template
description[REPLACE] Search for patterns, analyze findings, generate structured reports. Use when [REPLACE with specific triggers].
allowed-toolsGrep, Glob, Read, TodoWrite

Search-Analyze-Report Template

Purpose

This template demonstrates the Search → Analyze → Report workflow pattern for skills that systematically examine codebases and provide structured findings.

Use this template when:

  • Skill searches codebase for specific patterns
  • Analysis categorizes or prioritizes findings
  • Output is a structured report with recommendations

Workflow

1. Define search criteria 2. Use Grep/Glob to find matching files 3. Collect all findings systematically 4. Track locations for reporting

Phase 2: Analyze

1. Categorize findings by severity/type 2. Identify patterns across findings 3. Prioritize issues 4. Determine impact and recommendations

Phase 3: Report

1. Structure findings by category 2. Provide actionable recommendations 3. Include examples with file:line references 4. Summarize key takeaways

Progressive Disclosure

Core workflow (this file):

  • Search → Analyze → Report phases
  • High-level guidance

Detailed guidance (references/):

  • @references/security-analysis-example.md - Complete security audit example
  • Domain-specific patterns loaded when needed

Example Usage

<search>
Found 15 SQL injection vulnerabilities
Found 8 XSS vulnerabilities
Found 3 CSRF issues
</search>

<analyze>
Critical: 5 issues (immediate data exposure)
High: 12 issues (potential exploitation)
Medium: 9 issues (defense-in-depth)
</analyze>

<report>
## Critical Issues
1. Direct SQL concatenation at src/db.ts:45
   - Recommendation: Use parameterized queries

## High Priority Issues
...
</report>

See Also

  • @references/security-analysis-example.md - Full workflow demonstration