homeradar-fix-start

Classify HomeRadar bug severity and initiate the fix workflow.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill homeradar-fix-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: homeradar-fix-start
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/fix-start
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill homeradar-fix-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need a consistent, safe way to begin HomeRadar bug investigations, classify their severity, obtain required approvals, and set up the correct git worktree before writing code.

Core Features & Use Cases

  • Severity Classification: Guides the user to label the bug as SEV-1, SEV-2, or SEV-3.
  • SEV-1 Process: Requires a fix brief and explicit human approval before any work begins.
  • Worktree Creation: Automatically creates a fix/<slug> worktree from the latest development branch.
  • Commit Contract: Enforces standardized commit metadata referencing spec files and capability IDs.
  • Use Case: A developer discovers a critical regression (SEV-1) and uses this skill to document the issue, obtain manager sign‑off, and start a dedicated worktree for the fix.

Quick Start

Invoke the homeradar-fix-start skill to classify severity and set up the appropriate fix worktree.

Frequently Asked Questions about homeradar-fix-start

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a git worktree for a HomeRadar bugfix with proper severity triage?

To start a HomeRadar bugfix, classify the regression severity as SEV-1, SEV-2, or SEV-3. The workflow then guides you through fix brief creation, approval, and setting up a dedicated fix worktree from the development branch.

What is the required approval process for a critical SEV-1 regression bugfix?

For a SEV-1 regression bugfix, the process requires explicit human approval and mandatory fix brief documentation before any code work begins. This ensures critical bugs are properly reviewed before initiating the git worktree.

How do I enforce standardized git commit metadata for HomeRadar bug fixes?

Standardized git commit metadata is enforced by the bugfix workflow, requiring commit messages to reference specific spec files and capability IDs. This ensures traceability when committing regression fixes to the worktree.

Can I use this workflow to investigate SEV-2 and SEV-3 HomeRadar regressions?

Yes, the workflow applies to SEV-1, SEV-2, and SEV-3 regression investigations. It scales the fix brief and approval requirements based on the classified severity level before initiating the worktree setup.

When do I need to create a fix brief for a HomeRadar bug investigation?

A fix brief is mandatory for HomeRadar bug investigations, especially critical SEV-1 regressions requiring human sign-off. The brief documents the issue before creating the fix worktree and starting code changes.

Why does my HomeRadar bugfix workflow require a dedicated git worktree?

A dedicated fix worktree isolates the bugfix branch from the latest development branch. This allows safe regression investigation and standardized commits without disrupting the main development environment.