spinoff-issue

Convert out-of-scope work into linked GitHub issues with labels.

Updated May 3, 2026

Search Tags:#automation #github #scope management #labeling #issue creation #project hygiene #codebase triage

Ready to run

npx skills add https://github.com/ousiass/dotfiles --skill spinoff-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spinoff-issue
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/spinoff-issue
Command: npx skills add https://github.com/ousiass/dotfiles --skill spinoff-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps prevent PRs from becoming bloated by automatically extracting out-of-scope bugs, refactors, and feature requests into separate GitHub issues.

Core Features & Use Cases

Autonomous issue spin-off: Finds work that is outside the current scope and creates a new GitHub issue without asking the user.
Guardrails to prevent runaway issue creation: Performs deduplication, limits the number of creations per session, checks scope boundaries, and aborts on insufficient factual content.
Structured labeling and linkage: Applies consistent labels (type, area, severity/priority) and links the new issue back to the parent Issue and/or originating PR.

Quick Start

Ask the AI to convert an out-of-scope finding into a dedicated issue and include the parent issue number by calling: /spinoff-issue --parent #42.

Frequently Asked Questions about spinoff-issue

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

FAQPage Schema

How do I automatically extract out-of-scope work from a pull request into a GitHub issue?▼

To extract out-of-scope work from a pull request into a GitHub issue, an autonomous issue spin-off tool identifies scope spillover and creates a new issue without manual intervention. It converts discovered bugs, refactors, and feature requests into actionable items to keep PR scope focused.

What is issue segmentation in codebase triage and how does it prevent bloated PRs?▼

Issue segmentation in codebase triage is the process of separating out-of-scope work like bugs or refactors from the main task. It prevents bloated PRs by automatically converting this spillover into separate, actionable GitHub issues, keeping the original pull request focused on its intended scope.

Do I need GitHub CLI authentication to automate issue creation for scope spillover?▼

Yes, you need gh-authenticated GitHub CLI access to automate issue creation for scope spillover. The automation requires this authenticated access to perform deduplication, apply structured labels, and establish post-creation linkage back to the parent issue or originating PR.

How do I link a newly created GitHub issue back to its parent issue or originating PR?▼

To link a newly created GitHub issue back to its parent issue or originating PR, the issue creation process includes post-creation linkage. By initiating the spin-off with a command like /spinoff-issue --parent #42, the tool automatically connects the new issue to the specified parent.

What guardrails prevent runaway issue creation during automated codebase triage?▼

Guardrails that prevent runaway issue creation during automated codebase triage include deduplication checks, limits on the number of issues created per session, scope boundary verification, and automatic abortion on insufficient factual content. These ensure only valid, distinct out-of-scope items become issues.

How are labels structured when automating GitHub issue creation for out-of-scope bugs and refactors?▼

When automating GitHub issue creation for out-of-scope bugs and refactors, labels are structured consistently by type, area, and severity or priority. This structured labeling ensures newly segmented issues are properly categorized and linked back to the parent issue or originating PR.