You MUST use this skill before writing any fix or editing any code to address a bug. Use when the code should do X but currently does Y — restoring correct behavior in existing code. Stronger signals: error messages, stack traces, "not working", "broken", "failing", "regression", "it used to work". Use sextant:debug instead when you have a symptom but cannot yet point to a specific file or line. Use sextant:modify-feature instead when the requirement itself is changing, not just broken behavior.
$npx -y skills add hellotern/sextant --skill fix-bugInstalls into the current project.
Run `npx skills use "https://github.com/hellotern/sextant" --skill "hellotern/sextant/fix-bug"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/hellotern/sextant" that are relevant to the current task. Run `npx skills add "https://github.com/hellotern/sextant"` and select the relevant skills, then follow their instructions.