Skills analyze
๐Ÿ“ฆ

analyze

Content revision r2 Safe โš™๏ธ External commands

Analyze Existing Codebases in Depth

Existing codebases often lack a clear view of architecture, quality risks, and technical debt. This skill combines repository inspection with focused research and produces a prioritized Markdown report.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "analyze" from https://skillstore.io/skills/cubha-analyze.md and its manifest at https://skillstore.io/api/skills/cubha-analyze/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "analyze". Analyze the payment service and focus on architecture, security, and technical debt.

Expected outcome:

The report maps service layers and data flow, lists evidence-backed security concerns, ranks technical debt, and proposes immediate, short-term, and long-term actions.

Using "analyze". Review only the architecture of the existing customer portal.

Expected outcome:

The architecture review describes entry points, modules, dependencies, state flow, design patterns, scalability, and testability without modifying source files.

Using "analyze". Analyze the repository without external research and print the result in the terminal.

Expected outcome:

The terminal summary presents project maturity, architecture quality, confirmed code risks, technical debt totals, and prioritized improvements based only on repository evidence.

Security Audit

Safe
v3 โ€ข 7/23/2026 Open versioned report

All 33 external-command alerts are false positives caused by Markdown fences or inline code. The entropy alert reflects readable Korean documentation, not obfuscation. No malicious command behavior or prompt injection was found.

1
Files scanned
308
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/cubha-analyze/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/cubha-analyze/security.svg)](https://skillstore.io/skills/cubha-analyze?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/cubha-analyze?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cubha-analyze/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/cubha-analyze.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

cubha. (2026). analyze security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cubha-analyze/audits/3

BibTeX citation

@techreport{cubha-cubha-analyze-2026, author = {cubha}, title = {analyze security audit report (audit version 3)}, institution = {Skillstore}, year = {2026}, number = {3}, url = {https://skillstore.io/skills/cubha-analyze/audits/3}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "analyze security audit report (audit version 3)" version: "unspecified" type: report authors: - name: "cubha" date-released: "2026-07-23" url: "https://skillstore.io/skills/cubha-analyze/audits/3" identifiers: - type: other value: "skillstore:cubha-analyze:audit:3" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
85
Content
65
Community
83
Spec Compliance

What You Can Build

Audit a Legacy Service

Identify structural weaknesses, risky dependencies, technical debt, and practical improvements before maintaining or modernizing a legacy service.

Plan Engineering Improvements

Create an evidence-based roadmap that separates immediate fixes, short-term work, and longer architectural changes.

Assess Project Health

Summarize implementation maturity, stack suitability, security concerns, performance risks, and current technology guidance for planning decisions.

Try These Prompts

Run a Full Analysis
Analyze the existing codebase at {project_path}. Summarize its architecture, code quality, security, performance, technical debt, and prioritized improvements.
Review Architecture
Analyze {project_path} with --arch-only. Explain layers, data flow, module dependencies, patterns, scalability, and testability with file evidence.
Audit Code Quality
Analyze {project_path} with --quality-only. Focus on {risk_area}, testing gaps, error handling, performance bottlenecks, and high-confidence security issues.
Build a Research-Grounded Roadmap
Analyze {project_path} for {business_context}. Focus on {priority_risks}, reuse existing research, compare {core_technologies} with current guidance, and create a phased roadmap.

Best Practices

  • Run the skill from the project root so dependencies, documentation, and source paths resolve correctly.
  • State the analysis priority and project context in the request to improve relevance.
  • Review evidence and cited sources before scheduling roadmap work.

Avoid

  • Do not use this skill to design a project that has no existing code.
  • Do not include secrets or credentials in prompts, repository notes, or generated reports.
  • Do not treat every automated finding as confirmed without checking the referenced code.

Frequently Asked Questions

What projects can this skill analyze?
It analyzes existing brownfield codebases with source files, dependencies, and project documentation.
Does the skill modify application code?
No. It reads the codebase and writes only a dated analysis report unless terminal output is requested.
Does the analysis require internet access?
Full analysis uses Context7 and WebSearch. Use --no-research when external access is unavailable or unwanted.
Where is the report saved?
The report is saved under docs/analysis with a project slug and date in the filename.
Can I limit the analysis scope?
Yes. Use architecture-only, quality-only, no-research, or terminal-output options to control the workflow.
How does the skill handle sensitive information?
The workflow instructs agents to exclude secrets from reports. Review the report before sharing it outside the project.

Developer Details

Author

cubha

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

c43861a65bb95efcae259cd161c9d6f4dc7eec6f

Maintenance freshness

7/24/2026

Usage

2 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from cubha

View all
View all