Skip to content
Back to skills

Code Architecture Map

ASecurity

Build a compact architecture map of a repository using CGC, Semble, rg, and source reads.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 6, 2026
ai-agentsbash

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add 777genius/universal-plugins-for-ai-agents --skill code-architecture-map --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Architecture Map?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Architecture Map
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/777genius-code-architecture-map-universal-plugins-for-ai-agent/badge)](https://www.skillsdirectory.com/skills/777genius-code-architecture-map-universal-plugins-for-ai-agent)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-architecture-map
description: Build a compact architecture map of a repository using CGC, Semble, rg, and source reads.
execution_mode: docs_only
supported_agents:
  - codex
  - claude
---

# Code Architecture Map

## What it does

Creates a compact architecture map with entry points, core domains, adapters, risky files, verification points, and recommended next reads.

## When to use

Use this when entering a large repo, reviewing architecture, finding high-risk modules, or planning a multi-file change.

## How to run

1. Read project instructions first: `AGENTS.md`, `CLAUDE.md`, `README.md`, and package manifests.
2. Use `rg --files` to understand languages and major folders.
3. Use CGC stats and complexity to identify hotspots.
4. Use Semble for semantic entry points by feature or domain.
5. Read only the files needed to confirm the map.
6. Produce a short architecture summary with risks and next actions.

Commands:

```bash
rg --files | sed -n '1,160p'
cgc stats . --context "$(basename "$PWD")"
cgc analyze complexity --limit 25 --context "$(basename "$PWD")"
cgc report --output /tmp/CGC_REPORT.md --context "$(basename "$PWD")"
uvx --from semble==0.2.0 semble search -k 10 "main application flow" .
```

## Constraints

- Do not paste a giant file tree.
- Do not claim graph output is complete until source files confirm it.
- Prefer a useful map over inventory noise.
- Keep output focused on decisions, risks, and next reads.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…