nazgulcontextlisted

# Nazgul Context Collection ## Examples - `/nazgul:context` — Collect context based on the current objective type - `/nazgul:context refactor` — Collect context specifically for a refactor scope ## Current Project - Profile: !`head -20 nazgul/context/project-profile.md 2>/dev/null || echo "No profile — run /nazgul:init first"` - Architecture: !`head -20 nazgul/context/architecture-map.md 2>/dev/null || echo "No architecture map"` ## Arguments $ARGUMENTS ## Instructions Format all output per `references/ui-brand.md` — use stage banners, status symbols, and display patterns defined there. Collect targeted context based on the objective type. Write results to `nazgul/context/`. ### For Refactors 1. Identify ALL files in the refactor scope (use grep, glob) 2. Map their imports/exports to find the full dependency tree 3. Find ALL tests that cover these files 4. Find ALL callers of functions/classes being refactored 5. Check git blame for recent changes 6. Read the actual code of every file in scope 7. Document current behavior that must be preserved 8. Write findings to `nazgul/context/refactor-scope.md` ### For Bug Fixes 1. Trace the code path from entry point to error 2. Find related tests (passing and failing) 3. Check git log for recent changes to affected files 4. Write findings to `nazgul/context/bugfix-scope.md` ### For New Features 1. Find the most similar existing feature in the codebase 2. Map its implementation pattern (routes, handlers, services, models, tests