lucifer

Take a single GitHub issue (by number or URL) and drive it through an end-to-end flow (branch → plan → build → test → PR) using the `gh` CLI. All user interaction happens through issue comments, never the console. Use when the user says "implement issue

Triage and fix GitHub-reported security and quality findings — Dependabot alerts, code-scanning (CodeQL) alerts, and secret / malware scanning alerts — for this repository using `gh`, `npm`, and language-specific toolchains. Use when the user asks to review the Security tab, clear open alerts across any of the three surfaces, merge Dependabot PRs, or explain why an alert is safe to dismiss. Pairs with the `gh-cli-guide` skill for the underlying API calls. Does NOT auto-invoke `github-pr-fixer` — once a fix PR is opened, this skill stops and the owner chooses whether to run `/github-pr-fixer` manually.

Poll GitHub for open issues carrying a user-specified label and drive each one through gstack's end-to-end flow (plan → build → test → ship) via the `gstack-gh` skill. Use when the user says "watch GH for issues with label X and implement them", "auto-process the backlog", or "poll for ready stories". Supports three scheduling modes — in-session loop, self-paced loop, or cron (remote trigger).

Reproduce and fix reported bugs with test-first verification and root-cause analysis. Use when debugging a defect, investigating unexpected behavior, triaging a regression, or implementing a minimal corrective fix.

Scan the repository for stale, broken, or missing documentation and repair the highest-priority issues. Use when auditing docs, checking AGENTS links, reconciling docs with code, or running periodic documentation maintenance.

End-to-end workflow for adding a new feature from a task or prompt description. Use when implementing a new capability, adding an endpoint, introducing a new service method, or building a new UI component.

Improve code structure without changing behavior using safe, test-preserving refactoring steps. Use when extracting helpers, splitting files, reducing duplication, aligning with repository patterns, or cleaning up code.

End-to-end workflow for implementing a small scoped change while preserving every harness engineering invariant (dependency rules, tests, lint, structural checks, boundary validation, docs, ADRs, quality grades, versioning). Use for scoped single-domain tweaks that touch only a handful of files: tightening a validation, correcting a config default, adjusting a log line, updating a small piece of documented behavior, or making a narrow non-bug behavior adjustment. Not for defect investigation or corrective bug fixes (use `bug-fix`), not for multi-domain features (use `new-feature`), not for behavior-preserving restructure (use `refactor`).

Fetch SonarCloud issues for a project and break them down by severity using the SonarCloud Web API. Use when a prompt includes a SonarCloud project key and you need current issue counts or issue details for BLOCKER, CRITICAL, MAJOR, MINOR, and INFO severities, or when the user wants a fix-target list for high-severity, medium-severity, or BUG issues.