skills.rest
ousiass
ousiassCOMMUNITY
Explore all skills by this author →
GitHub

spinoff-issue-en

Create standalone GitHub Issues for out-of-scope implementation work.

Updated May 3, 2026
Search Tags:#code review#workflow automation#github#project governance#labeling#issue creation#pr hygiene
One-click install
npx skills add https://github.com/ousiass/dotfiles --skill spinoff-issue-en
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spinoff-issue-en
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/spinoff-issue-en
Command: npx skills add https://github.com/ousiass/dotfiles --skill spinoff-issue-en

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

It prevents PRs from becoming bloated by automatically turning discovered out-of-scope work into a separate GitHub Issue with the right labels and acceptance criteria.

Core Features & Use Cases

  • Creates a separate GitHub Issue post-hoc for independent bugs, features, refactors, or doc/spec mismatches found during implementation.
  • Applies consistent issue taxonomy using labels like type, area, and severity/priority, plus a spinoff marker for easy discovery.
  • Safeguards against runaway issue creation via duplicate checks, volume limits, and an empty-content verification requirement.

Quick Start

Ask Claude to spin off work discovered during implementation by providing a short summary and the parent issue number, for example: “/spinoff-issue-en --parent #42 add retry behavior to the login screen”.

Frequently Asked Questions about spinoff-issue-en

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

FAQPage Schema
How do I spin off out-of-scope work into a GitHub issue during code review?▼

To spin off out-of-scope work into a GitHub issue, the Skill automatically creates a standalone issue using the gh CLI, populating it with affected code, acceptance criteria, and validated labels without requiring user confirmation.

How do I prevent PR bloat from independent bugs or refactors found during implementation?▼

Preventing PR bloat from independent bugs or refactors involves moving that work into a separate GitHub issue. The Skill applies issue taxonomy labels and a spinoff marker to track the discovered work independently from the current PR.

Can I automatically create GitHub issues for discovered work using gh CLI?▼

Yes, you can automatically create GitHub issues for discovered work using gh CLI. The Skill enforces auto-creation guards, applies validated labels, and uses an issue template to structure the body with acceptance criteria.

What safeguards exist against runaway issue creation when spinning off PR work?▼

Safeguards against runaway issue creation when spinning off PR work include duplicate checks, volume limits, and an empty-content verification requirement to ensure only valid out-of-scope tasks become issues.

Does the Skill require user confirmation before creating a new GitHub issue?▼

No, the Skill does not require user confirmation before creating a new GitHub issue. It automatically generates the standalone issue during code-review and implementation workflows to prevent the current PR from bloating.

Related Skills

Explore More Software Engineering Skills→
gqf2008gqf2008

github-auth

Authenticate Hermes Agent with GitHub via gh CLI or git tokens and SSH keys.

Community
Intermediate
amdmaxamdmax
2

finalize-story

Update GitHub issues, link pull requests, apply labels, and add stories to project boards.

Community
Advanced
mlflowmlflow
1

fetch-diff

Fetch GitHub PR diffs with line numbers and filtered files.

Official
Advanced
ousiassousiass

spinoff-issue

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

Community
Advanced