Software Development
Import Graph Analyzer
Import Graph Analyzer turns code quality & refactoring material into an operator-ready artifact with a concrete dependency direction map, cycle detection, and module-boundary repair path. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for code excerpts, dependency map, or static-analysis notes, complexity, duplication, or naming concerns, and risk tolerance and test coverage context up front, then organizes the output around import, graph, analyzer, code, and quality. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. Import Graph Analyzer is scoped to the Code Quality & Refactoring workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.
One-Time Purchase
$19.99
Import Graph Analyzer — Sample Brief
Headline
Builds a code-quality repair plan for import graph analyzer work, turning code excerpts, dependency map, or static-analysis notes, complexity, duplication, or naming concerns, and risk tolerance and test coverage context into dependency direction map, cycle detection, and module-boundary repair path. In this example, target repository module needs a repository-backed review with commands, files, and acceptance tests that engineering can rerun. The output is a concrete operator-ready artifact: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| code excerpts, dependency map, or static-analysis notes | target repository module needs a repository-backed review with commands, files, and acceptance tests that engineering can rerun. | Provided |
| complexity, duplication, or naming concerns | Three representative examples from the current workflow | Reviewed |
| risk tolerance and test coverage context | Approval threshold and final reviewer | Confirm |
| desired refactor size and review path | Code Quality & Refactoring owner and downstream audience | Ready |
Import Evidence Model
| Field | What must be captured | Review consequence |
|---|---|---|
| Import signal | Anchor the result in import, graph, and analyzer evidence from the supplied material. | Treat as draft until dependency direction map is source-backed. |
| Dependency Direction Map | Separate Import signal, Graph judgment, and Analyzer action before drafting. | Escalate when import evidence is missing or contradicted. |
| Cycle Detection | Name the review question that makes Import Graph Analyzer different from the rest of Code Quality & Refactoring. | Reviewer resolves module-boundary repair path before final use. |
Import Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| Import depth | Anchor the result in import, graph, and analyzer evidence from the supplied material. | Keep, revise, or ask a targeted follow-up |
| Graph boundary | Separate Import signal, Graph judgment, and Analyzer action before drafting. | Confirm this is not a renamed adjacent bundle skill |
| Analyzer handoff | Name the review question that makes Import Graph Analyzer different from the rest of Code Quality & Refactoring. | Assign the owner decision before final use |
Import Graph Analyzer Work Map
Import Graph Analyzer focus areas
Draft Operator Ready Artifact
| Import signal | Dependency Direction Map | Cycle Detection | Module Boundary Repair Path | Graph decision |
|---|---|---|---|---|
| Import | dependency direction map | cycle detection | module-boundary repair path | Keep if source-backed |
| Graph | dependency direction map | cycle detection | Import evidence is missing or contradicted. | Revise missing evidence |
| Analyzer | Anchor the result in import, graph, and analyzer evidence from the supplied material. | Separate Import signal, Graph judgment, and Analyzer action before drafting. | module-boundary repair path | Assign owner decision |
Use now
Import Graph Analyzer
Best when code quality & refactoring work needs a concrete operator-ready artifact.
Hold back
Missing evidence
Best deferred when a key input would change the artifact.
Reviewer note
The output is structured so an operator can validate the draft, edit the artifact, and hand it to the next owner without re-reading the entire packet. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.
This sample illustrates the skill's output format. The artifact reviewed is illustrative and should be validated against the real repository before implementation.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Code Quality & Refactoring
Bundle price: $44. Compare this skill with the full workflow bundle or Pro access.
Best for
Engineers untangling module dependencies — direction map, cycle detection, and a boundary-repair path. Most useful on a codebase where circular imports or a tangled dependency graph make changes ripple unpredictably.
Not ideal for
Small or flat codebases with no real graph to analyze, and runtime performance profiling. It maps the structure — an engineer decides which boundaries are worth enforcing and does the refactor.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short setup in the repository or workspace where the skill will run. Some coding familiarity helps for implementation-heavy outputs.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.