Agent skill · Security

enterprise-code-analyzer

Three-tier enterprise code analysis system. Tier 1 analyzes individual repositories (structure, patterns, dependencies, memory). Tier 2 maps cross-repository relationships (API contracts, shared libraries, service coupling). Tier 3 provides enterprise governance (technology portfolio, technical debt, security audit, strategic recommendations). Generates local .memory folders, .cursorrules files, and governance reports.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill enterprise-code-analyzer-anivar-enterprise-code-anal --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.0.0
Declared author: anivar
Requires: Requires git and gh (GitHub CLI). Optional: jq for JSON parsing, curl for OpenMemory sync.
Path: skills/analysis/enterprise-code-analyzer-anivar-enterprise-code-anal/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Enterprise Code Analyzer Three-tier system for enterprise-wide code understanding. Analyzes individual repositories, maps cross-repository relationships, and provides governance-level insights. ## Architecture ``` Tier 1: Repository Analysis (individual repo structure, patterns, memory) | v Tier 2: Cross-Repo Analysis (relationships, API contracts, dependencies) | v Tier 3: Enterprise Governance (portfolio, debt, security, strategy) ``` Each tier builds on the previous. Run sequentially for full analysis, or use individual tiers independently. ## When to Apply Reference these guidelines when: - Setting up code memory for a new repository - Understanding repository architecture and patterns - Finding dependencies between services - Identifying API contract mismatches - Running enterprise-wide technology assessments - Evaluating technical debt across repositories - Conducting security and compliance audits - Making strategic technology decisions ## Priority-Ordered References | Priority | Reference | Tier | Description | |----------|-----------|------|-------------| | 1 | `repo-analysis.md` | 1 | Individual repo structure, patterns, dependencies, memory creation | | 2 | `cross-repo

What's inside
Steps it walks through
  1. Architecture
  2. When to Apply
  3. Priority-Ordered References
  4. Quick Reference
  5. Tier 1: Repository Analysis
  6. Tier 2: Cross-Repository Relationships
  7. Tier 3: Enterprise Governance
  8. Problem to Reference Mapping
  9. Full Compiled Document
  10. Usage Examples
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the enterprise-code-analyzer skill do?

Three-tier enterprise code analysis system. Tier 1 analyzes individual repositories (structure, patterns, dependencies, memory). Tier 2 maps cross-repository relationships (API contracts, shared libraries, service coupling). Tier 3 provides enterprise governance (technology portfolio, technical debt, security audit, strategic recommendations). Generates local .memory folders, .cursorrules files, and governance reports.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill enterprise-code-analyzer-anivar-enterprise-code-anal --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going