navgator

Plugin navgator from marketplace navgator in tyroneross/NavGator. Commands read from the repo's manifest — 2 days ago.

Skills (6)

• architecture-export

  Use when user asks to show or generate an architecture diagram, visualize dependencies, export architecture docs, create architecture documentation, save architecture output, or create a mermaid diagram of their project.

• architecture-scan

  Use when user asks to scan architecture, check dependencies, find outdated packages, show project structure, refresh architecture, or run a health check. Navgator scan, status, and staleness check.

• code-review

  Architectural integrity review of changes already made — system flow, connections, drift. Use when user asks to review architecture, check connections, navgator review, is this safe to merge, what did I break, or when scan detects architectural drift. Not for forecasting the effect of a change you h

• impact-analysis

  Forecasts the blast radius of a change before you make it — dependencies, connections, data flow. Use when user asks what breaks if I change X, impact of changing, what depends on, trace data flow, show connections, dependency graph, upstream/downstream, or safe to modify before refactoring. Not for

• infrastructure-scanning

  Detects and analyzes infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, type validation. Use when user asks about database schema/models, environment variables, queue or cron setup, deploy config, or whether Prisma types match TypeScript. Not for general

• navgator-setup

  Use when user asks to install navgator, update navgator, set up navgator, launch the dashboard, or run navgator ui maintenance.

Slash commands (4)

• /navgator:feedback

  Report a bug or send feedback about the navgator plugin

• /navgator:gator

  Main NavGator router. Dispatches to a subcommand based on your request, or lists options if unclear. Use `/navgator:<subcommand>` to target a specific action directly.

• /navgator:plan

  Plan an architecture change or investigation using NavGator (delegates to architecture-planner agent)

• /navgator:scan

  Quick architecture scan — refresh component and connection tracking

Subagents (4)

• architecture-advisor

  Specialized agent for architecture decisions, dependency management, and impact analysis. Use when planning significant changes to the tech stack.

• architecture-investigator

  Autonomous subagent for investigating architecture issues using the navgator CLI. Follows SRE-style read-only investigation before proposing changes. Deploy via the Task tool when a specific component, violation, or data-flow issue needs deep analysis.

• architecture-planner

  Use this agent when the user's request requires understanding the architecture before answering — phrasings like "review architecture for X", "what's the blast radius of changing Y", "is the graph fresh", "investigate the auth flow", "should I refactor Z", "how does this connect to that", "trace thi

• external-resolver

  Use this agent when NavGator needs its external boundary nodes (npm/pip/spm/cargo/go/service/llm/infra) resolved or refreshed against upstream registries — attaching canonical identity, latest version, release date, docs URL, and a freshness verdict. Typical triggers include the staleness sweep find

Similar plugins