architectural-analysis
Audit Codebase Architecture
Large codebases collect dead code, duplicate logic, and unclear boundaries over time. This skill guides Claude, Codex, or Claude Code through a structured architecture audit.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "architectural-analysis" from https://skillstore.io/skills/cygnusfear-architectural-analysis.md and its manifest at https://skillstore.io/api/skills/cygnusfear-architectural-analysis/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 "architectural-analysis". Review a TypeScript service before a refactor.
Expected outcome:
A Markdown audit listing dead files, unused exports, duplicate utilities, architecture issues, and cleanup estimates.
Using "architectural-analysis". Assess a legacy frontend for maintainability risks.
Expected outcome:
A prioritized report covering large components, layer violations, unsafe type usage, repeated logic, and suggested ownership areas.
Using "architectural-analysis". Prepare cleanup work for a sprint planning meeting.
Expected outcome:
A concise summary with top dead files, duplicate groups, architectural risks, and verification notes for uncertain findings.
Security Audit
SafeStatic findings are false positives caused by Markdown backticks, fenced examples, and local analysis commands in SKILL.md. No evidence found of code execution payloads, credential access, network exfiltration, or prompt injection intent.
Risk Factors
โ๏ธ External commands (82)
๐ Filesystem access (1)
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.
Copy report link
https://skillstore.io/skills/cygnusfear-architectural-analysis/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cygnusfear-architectural-analysis?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cygnusfear-architectural-analysis?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cygnusfear-architectural-analysis/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cygnusfear-architectural-analysis.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
Cygnusfear. (2026). architectural-analysis security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cygnusfear-architectural-analysis/audits/8BibTeX citation
@techreport{cygnusfear-cygnusfear-architectural-analysis-2026,
author = {Cygnusfear},
title = {architectural-analysis security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cygnusfear-architectural-analysis/audits/8},
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: "architectural-analysis security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Cygnusfear"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/cygnusfear-architectural-analysis/audits/8"
identifiers:
- type: other
value: "skillstore:cygnusfear-architectural-analysis:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare A Refactor Plan
Identify dead code, duplicate modules, and architecture risks before assigning cleanup work.
Review A Legacy Codebase
Map structural problems and estimate cleanup impact before changing inherited code.
Improve TypeScript Health
Find unsafe type usage, duplicate interfaces, and code smells that reduce maintainability.
Try These Prompts
Use the architectural-analysis skill to review this repository. Focus on dead code, duplicate logic, and the highest impact cleanup opportunities.
Use the architectural-analysis skill on this TypeScript project. Prioritize type confusion, unsafe any usage, duplicate types, and module boundaries.
Use the architectural-analysis skill to find refactor candidates. Rank dead files, duplicate utilities, large modules, cycles, and layer violations by impact.
Use the architectural-analysis skill for a full repository audit. Create the report, quantify cleanup potential, and separate confirmed issues from items needing verification.
Best Practices
- Run the audit from the repository root so path searches cover the full project.
- Verify possible dead code against dynamic imports, framework hooks, and public API contracts.
- Use the generated report as a planning artifact before making cleanup changes.
Avoid
- Do not delete files directly from the audit results without manual verification.
- Do not treat similar names as duplication until the underlying logic is compared.
- Do not skip tests, generated boundaries, or entry points when deciding whether code is unused.
Frequently Asked Questions
Does this skill modify my code?
Which languages does it fit best?
Can it find all dead code automatically?
What output should I expect?
Why does it use shell examples?
Can Claude Code or Codex use it?
Developer Details
Author
CygnusfearLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7e9e368dc1a370f2040369ebcd0db06d90cb48e5
Maintenance freshness
7/20/2026
Usage
5 downloads ยท 271 views
File structure
๐ SKILL.md