analyze

Analyze codebases, documents, or systems from six analysis angles.

Updated May 9, 2020

Search Tags:#code review #analysis #document analysis #structured findings #system review

Ready to run

npx skills add https://github.com/tkstang/sequence --skill analyze-tkstang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/tkstang/sequence/tree/main/.agents/skills/analyze
Command: npx skills add https://github.com/tkstang/sequence --skill analyze-tkstang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, multi-angle analysis of existing artifacts, codebases, documents, or systems, offering structured findings and prioritized recommendations to improve them.

Core Features & Use Cases

Multi-Angle Analysis: Examines targets from six analysis angles (Adversarial, Gap, Opportunity, Structural, Consistency, Audience).
Structured Findings: Delivers organized insights with prioritized recommendations.
Use Case: Analyze a codebase for quality and improvement opportunities, or review a document for completeness and clarity.

Quick Start

Use the analyze skill to analyze the code in the 'src/auth/' directory.

Frequently Asked Questions about analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I conduct a multi-angle code review for a specific directory?▼

To conduct a multi-angle code review, target a specific directory to examine code from adversarial, gap, opportunity, structural, consistency, and audience angles, yielding structured findings with prioritized recommendations.

What is the best way to analyze a document for completeness and clarity gaps?▼

Analyzing a document for completeness and clarity involves applying gap and consistency analysis angles to the text input, which identifies structural weaknesses and outputs prioritized recommendations for improvement.

Do I need Python installed to run system review and structured findings analysis?▼

Yes, you need Python installed because the analysis execution and the generation of structured findings rely on specific Python libraries to process file paths, directories, and text inputs.

Can I use this approach to review a whole codebase or just single files?▼

You can review a whole codebase or single files because the analysis supports multiple input types, accepting individual file paths, entire directories, or direct text inputs for comprehensive examination.

What distinguishes an adversarial and structural analysis from standard linting?▼

Adversarial and structural analysis differs from standard linting by evaluating system logic, audience alignment, and opportunity gaps rather than just syntax, delivering prioritized recommendations for architectural improvements.

When should I avoid using automated multi-angle analysis for my artifacts?▼

You should avoid automated multi-angle analysis when your artifacts lack sufficient structural complexity or when text inputs are too fragmented, as comprehensive findings require coherent file paths or directories to evaluate.