hoangsa

Manage worker-rules addons — list available, add/remove addons interactively. Use when the user wants to see available addons, enable/disable framework-specific worker rules, or says "addon", "addons", "worker rules".

Audit the codebase — scan for code smells, architecture issues, security risks, performance problems, and tech debt → AUDIT-REPORT.md. Use when the user wants a health check, code review, wants to find problems before refactoring, says "audit", "review codebase", "find issues", "tech debt", or needs a comprehensive analysis of what needs fixing.

Brainstorm an idea — explore intent, propose approaches, validate design → BRAINSTORM.md. Use BEFORE /hoangsa:menu when you have a vague idea and want to explore it collaboratively before committing to a spec. Output feeds directly into the menu workflow.

Initialize HOANGSA for a project — detect codebase, setup preferences, model routing. Run once when starting a new project. Use when the user says "init", "setup project", "first time", or when .hoangsa/config.json doesn't exist yet.

Status — show session progress with wave structure, budget usage, and artifacts. Use when the user asks "how's it going", "what's the status", "show progress", or wants an overview of the current session.

Quality gate reviewer — checks implementation against acceptance criteria and reports pass/fail with evidence.

Simplify pass worker — reviews recently-changed files for code quality issues, duplication, and unnecessary complexity.

Implementation worker — executes a single task from the HOANGSA plan with write access to the task's files.

Read-only worker for research and analysis tasks — cannot modify files.

This skill should be used when the user is building, changing, or trying to verify a frontend feature on web (React/Vite) or React Native/Expo, and is unsure how to prove it actually works. Triggers on phrases like 'how do I test this component/screen', 'verify this feature', 'make sure this works on web/mobile', 'is this covered by tests', 'my tests pass but the feature is broken', 'no tests yet', or before shipping any FE change. Guides the full loop: define verifiable success criteria before coding, write tests at the correct layer (logic/component/E2E/visual), and confirm behavior by running the real app.

This skill should be used when the user wants to start a new task, switch between tasks, park or resume work, finish a task (push + PR), clean up merged branches, or sync with upstream. Triggers on phrases like 'start task', 'new task', 'work on', 'switch to', 'park this', 'resume', 'continue where I left off', 'done with this', 'finish task', 'create PR', 'clean branches', 'delete merged', 'rebase', 'pull latest', or 'sync with main'.

Use when the user needs to run hoangsa-memory CLI commands — setup / index / query / watch / impact / context / changes / graph / memory / skills / eval / uninstall. Examples: "index this repo", "show memory", "trace the graph", "find taint paths", "uninstall hoangsa-memory".

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", "who calls this method?", "this endpoint returns 500".

This skill should be used before any non-trivial coding action — editing code, writing new files, running migrations, deploying, or answering a question that involves factual claims about this codebase. It forces the agent to consult hoangsa-memory's persistent memory (USER.md, MEMORY.md, LESSONS.md, the indexed code graph) and acknowledge relevant lessons before acting. Trigger phrases: "edit", "refactor", "implement", "fix the bug in", "add a feature", "deploy", "why does this do", "how does X work".