agentsclimarketplace

Component extraction and tactical forking analyzer

Skill anyulled/architecture-guardrails-skills/skills/component-extraction-and-tactical-forking-analyzer

Agent-agnostic software architecture guardrails skills collection

Install
npx -y skills add anyulled/architecture-guardrails-skills --skill component-extraction-and-tactical-forking-analyzer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze monolithic codebases to identify extraction candidates, shared-kernel entanglement, and tactical forking effort. Use when planning modernization or breaking a monolith into independently deployable domains.

SKILL.md

2.4 KB, 430 tokens by cl100k_base, as published. Nobody here has run it

Component Extraction and Tactical Forking Analyzer

Identify bounded contexts that are suitable for extraction from a monolith.

When to Use

  • Modernization or decomposition planning
  • Legacy monolith audits
  • Pre-extraction feasibility studies
  • Domain boundary or context-map reviews

Scope

  • Scans: namespace and directory structures, cross-domain imports, and shared Common/Shared/Core/Utils directories to identify extraction candidates.
  • Exclusions: benign technical shared code, generated/vendor code, and sample or reference repos that are not candidates for extraction.
  • Fallback: if domain ownership is unclear, apply the shared conventions heuristic order and report a warning with low confidence.
  • Routing: defer bounded-context leakage to Domain Boundary and Language Integrity Evaluator and module-level coupling health to Structural Coupling and Volatility Analyzer.

Workflow

  1. Map domain components.
    • Group code by namespace or directory.
    • Compare internal cohesion with external coupling.
  2. Identify shared-kernel entanglement.
    • Trace dependencies into Common, Shared, Core, or Utils.
    • Separate benign helpers from malignant shared domain state.
  3. Estimate tactical forking effort.
    • Simulate a fork for the best candidate.
    • Count severed references, broken dependencies, and entangled classes.
  4. Report findings.
    • Rank the top extraction candidates.
    • Provide an extraction effort score and blocker summary.

Rules

  • Use static analysis and AST dependency graphs only.
  • Do not mutate files or simulate changes beyond analysis.
  • Keep the analysis deterministic and language-agnostic.

Shared Conventions

  • Follow the repository-wide conventions in shared-skill-conventions.
  • Use the canonical output contract, severity levels, confidence rubric, routing rules, and false-positive downgrades defined there.
  • If this skill is not the closest match, defer to the routing guidance in the shared conventions file.

Output

Return:

  • Top extraction candidates
  • Shared-kernel blockers
  • Tactical forking effort score
  • CI-ready or planning-ready markdown/JSON report

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.