Back to list
thoreinstein

analyze

by thoreinstein

My opencode configurations, agents, commands and everything else

1🍴 0📅 Jan 15, 2026

SKILL.md


name: analyze description: Deep analysis mode - thorough multi-phase investigation with expert consultation

DEEP ANALYSIS MODE

Current Time: !date

Perform a comprehensive analysis using multi-phase expert consultation and parallel research.

Analysis Protocol

Phase 1: Reconnaissance (Parallel Swarm)

Launch immediately:

background_task(agent="explore", prompt="Map relevant code structure...")
background_task(agent="explore", prompt="Find related patterns...")
background_task(agent="librarian", prompt="Research best practices for...")

While swarm runs, use direct tools:

  • glob to find relevant files
  • grep to identify patterns
  • read to understand key code

Phase 2: Expert Analysis

Based on findings, consult specialists:

DomainAgentFocus
Architecture@architectSystem design, data flow, dependencies
Security@securityVulnerabilities, threat model, risks
Reliability@sreScalability, SLOs, observability
Performance@perfProfiling, bottlenecks, optimization
Patterns@principalCode quality, best practices, tradeoffs

Phase 3: Deep Dive

Analyze comprehensively:

  • Edge cases and potential failure modes
  • Performance implications under load
  • Security attack surface
  • Error handling completeness
  • Testability and maintainability
  • Technical debt assessment

Phase 4: Synthesis

Combine findings into actionable output:

## Executive Summary

[2-3 sentences: key findings and recommendation]

## Detailed Analysis

### Architecture

[Component analysis, data flow, dependencies]

### Code Quality

[Patterns, anti-patterns, maintainability]

### Security

[Vulnerabilities, risks, compliance]

### Performance

[Bottlenecks, scalability concerns]

## Issues Found

### Critical (P0)

- [Issue with location and impact]

### High (P1)

- [Issue]

### Medium (P2)

- [Issue]

## Recommendations

### Immediate Actions

1. [Action with rationale]

### Short-term Improvements

1. [Improvement]

### Long-term Considerations

1. [Consideration]

## Trade-offs

[Analysis of different approaches with pros/cons]

Analysis Focus Areas

AreaWhat to Examine
CorrectnessLogic errors, edge cases, assumptions
SecurityInput validation, auth, data protection
PerformanceComplexity, caching, resource usage
ReliabilityError handling, failure modes, recovery
MaintainabilityReadability, coupling, documentation
TestabilityCoverage, mocking, isolation

Output

Write to Obsidian via obsidian_append_content at: $OBSIDIAN_PATH/Analysis/YYYY-MM-DD-target.md

Note: $OBSIDIAN_PATH must be a vault-relative path (e.g., Projects/myapp), set per-project via direnv. The obsidian_append_content tool expects paths relative to the vault root.

Document Structure

Use this template for the Obsidian document:

@~/.config/opencode/templates/analysis-report.md

Analyze

$ARGUMENTS

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon