Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
Optimize any repository for minimal-token agent onboarding — llms.txt, AGENTS.md, hidden HTML agent blocks, docs/agents.md. Use when asked to improve agentic access, agent metadata, llms.txt, or run the agent-access optimizer subagent on a project.
Compose ACL, task graph, scheduler, merge, and related coordination subsystems via metagit aos|coord status|doctor|next. Use when an operator or orchestrator needs one snapshot of coordination health or the next work envelope without launching models. Start with the day-1 quickstart for the canonical control loop.
Plan and track cross-project multi-repo campaigns — YAML overlays, repo rollups, objective fan-out, and MR status. Use for umbrella-scale coordinated work.
CLI-only shortcuts for metagit agents — workspace catalog, discovery, prompts, sync, layout, and config. Use instead of MCP or HTTP API when operating from a shell or agentmode session.
Refresh or bootstrap .metagit.yml using deterministic discovery and validation flows. Use when configuration is missing, stale, or incomplete for workspace operations.
Token-efficient workspace onboarding via tiered context packs — map, repo cards, session digest, objectives, approvals, repomix profiles. Use at session start or when scoping work in a metagit-managed workspace.
Run gitnexus analysis for a target workspace and selected project repositories before graph-dependent tasks. Use when index staleness is detected or cross-repo graph results are needed.
Discover, suggest, promote, validate, and ingest cross-repo graph.relationships in .metagit.yml for GitNexus overlay and dependency maps. Use for first-time graph bootstrap or ongoing workspace graph maintenance.
Token-efficient MCP resource ladder for metagit workspaces — catalog, map, layered prompts, project/repo drill-down. Use when the IDE host exposes metagit resources/read instead of shell CLI.
Coordinate implementation tasks across multiple repositories using metagit status, search, and scoped sync workflows. Use when one objective spans several repositories.
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
Mandatory before calling work complete when the session changed repo files. Runs format, lint, tests, integration tests, context-aware pip-audit/bandit, and optional gitleaks via task qa:prepush. Use before push, release, or hand-off.
Plan repository change impact before edits by combining metagit workspace context and graph-based dependency analysis. Use when a change may affect multiple repositories.