Skip to content

feat: add ponytail-github-issues skill - #684

Open
stareezy-1 wants to merge 1 commit into
DietrichGebert:mainfrom
stareezy-1:feat/github-issues-skill
Open

feat: add ponytail-github-issues skill#684
stareezy-1 wants to merge 1 commit into
DietrichGebert:mainfrom
stareezy-1:feat/github-issues-skill

Conversation

@stareezy-1

Copy link
Copy Markdown

What

Adds ponytail-github-issues — a skill for finding and fixing open-source GitHub issues the ponytail way: smallest diff, root cause, one PR, ship.

Files

  • skills/ponytail-github-issues/SKILL.md — full skill (Kiro / OpenClaw format)
  • .kiro/steering/ponytail-github-issues.md — Kiro steering format

What it covers

  • Workflow: CONTRIBUTING.md first → discover → read → root cause → ladder → check → comment → PR
  • Issue ladder: stop at the first rung (already being fixed? → docs one-liner? → missing guard? → wrong value? → missing case? → structural fix)
  • Discovery signals: how to find issues where the reporter won't fix it themselves
  • CLA table: Meta, Google, Expo — sign before PRs
  • Rules: one issue per PR, root cause not symptom, match existing style, no drive-bys, fewest files

Why

The ponytail philosophy maps perfectly to open-source contributions: the laziest correct fix is a one-line guard in the shared path, not fifty lines across every caller. This skill channels that into a repeatable workflow for finding actionable issues, shipping minimal PRs, and not wasting maintainer review time on over-engineered fixes.

Tested against expo/expo, facebook/react, and facebook/react-native — 10 PRs submitted using this workflow, all focused single-file or two-file fixes.

Adds a skill for finding and fixing open-source GitHub issues the lazy
way: smallest diff, root cause fix, one issue per PR, no drive-by
refactors.

Includes:
- skills/ponytail-github-issues/SKILL.md (full skill)
- .kiro/steering/ponytail-github-issues.md (Kiro steering format)

Covers: issue discovery signals, CLA requirements table, workflow
(CONTRIBUTING → discover → read → root cause → ladder → check →
comment → PR), and the issue-fixing ladder.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant