kissue

Delivers bounded GitHub issues as pull requests with regression tests and Closes references.

2|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/kpiteira/devops-ai --skill kissue-kpiteira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kissue
Source: https://github.com/kpiteira/devops-ai/tree/main/skills/kissue
Command: npx skills add https://github.com/kpiteira/devops-ai --skill kissue-kpiteira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a well-defined GitHub issue into a merged pull request involves repetitive manual steps: fetching the issue, reproducing the defect, writing regression tests, branching, committing, and opening a PR. This Skill automates that entire maintenance workflow for defects, chores, and narrowly scoped changes. ## Core Features & Use Cases - Issue Contract Establishment: Fetches the full issue, linked PRs, discussion, and repository state to identify the observable failure, invariants, and scope fences before writing code. - Test-First Delivery: Reproduces the defect, implements the fix, adds regression coverage, and runs the repository's standing gates without weakening existing tests. - PR Automation: Creates an issue branch, commits coherently, and opens a PR stating the observable outcome with a Closes #N reference. - Use Case: A user points at issue #42 reporting a broken validation rule; the Skill reproduces the failure, fixes the code, adds a regression test, and opens a PR that closes the issue. ## Quick Start Ask the assistant to fix GitHub issue 42 and deliver it as a pull request using the kissue workflow.

Frequently Asked Questions about kissue

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

FAQPage Schema
How do I turn a GitHub issue into a pull request automatically?

Point the Skill at an issue number and it fetches the issue, reproduces the defect, implements the fix with regression tests, and opens a PR containing a Closes #N reference. It works best for defects and narrowly scoped changes.

What kinds of GitHub issues can kissue handle?

kissue handles defects, chores, and narrowly scoped changes whose desired outcome is already observable in the issue. Feature-sized work, multi-milestone efforts, or issues lacking an independent definition of done are routed to the kspec planning skill instead.

When should I use kspec instead of kissue?

Use kspec when the work involves new product capabilities, consequential design choices, multiple milestones, or material ambiguity. kissue stops and routes to planning rather than inventing product intent when the issue contract is unclear.

Does kissue modify existing tests when fixing a bug?

No, kissue does not weaken existing tests or architecture contracts. It adds new regression coverage for the fix and runs the repository's standing gates to verify nothing breaks.

What happens if the issue cannot be resolved as stated?

The Skill records a concrete blocker instead of opening a success-shaped PR around incomplete work. If the issue's stated facts no longer match the code, it stops and routes the work to planning.