lifecycle-issue-fixer

Resolve GitHub issues via TDD, worktree isolation, and pull request creation.

168|55|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/tile-ai/TileOPs --skill lifecycle-issue-fixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lifecycle-issue-fixer
Source: https://github.com/tile-ai/TileOPs/tree/main/.claude/skills/lifecycle-issue-fixer
Command: npx skills add https://github.com/tile-ai/TileOPs --skill lifecycle-issue-fixer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, python, pytest, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the full lifecycle of closing a GitHub issue by reading the issue, creating an isolated worktree if needed, driving a test-first implementation, verifying results, and opening a pull request, removing manual orchestration and reducing human error.

Core Features & Use Cases

  • Issue ingestion & validation: Parses issue references or URLs, fetches issue details and comments, and enforces a required issue template before any work begins.
  • Safe worktree management: Detects existing worktrees or clean feature branches and creates an isolated worktree when necessary to avoid disrupting the main branch.
  • TDD-driven implementation: Enforces a strict red-green-refactor cycle, runs targeted tests using a provided script, and updates a context file describing affected files, tests, and benchmarks.
  • Independent verification & PR lifecycle: Dispatches an independent verification subagent to validate acceptance criteria and then invokes a lifecycle PR skill to commit, create, and manage the PR.

Quick Start

Resolve issue 123 by running the end-to-end TDD workflow: read the issue, create or enter a worktree, write failing tests, implement the fix until tests pass, run independent verification, and open a PR.

Frequently Asked Questions about lifecycle-issue-fixer

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

FAQPage Schema
How do I automate GitHub issue resolution using test-driven development?

Automating GitHub issue resolution with TDD involves parsing issue metadata, enforcing template guard rails, creating an isolated worktree, writing failing tests, implementing the fix, and opening a pull request. This Skill orchestrates that end-to-end red-green-refactor lifecycle.

What is a git worktree and when do I need it for pull request automation?

A git worktree provides an isolated branch environment. You need it for pull request automation when resolving issues to avoid disrupting the main branch, allowing safe test execution and feature implementation before committing changes.

How do I run targeted tests for a specific GitHub issue fix?

Running targeted tests for a specific GitHub issue fix requires executing a run-affected-tests.sh script within an isolated worktree. This validates only tests related to the changed files during the TDD cycle.

Does this TDD workflow require pytest and jq to function?

Yes, this TDD workflow requires pytest and jq to function. Python and pytest drive the test automation, while jq parses the GitHub issue metadata required to enforce template and assignee guard rails before implementation begins.

What is the best way to verify acceptance criteria before creating a pull request?

The best way to verify acceptance criteria before creating a pull request is dispatching an independent verification subagent. This validates the TDD implementation against the original GitHub issue requirements before invoking the PR lifecycle management process.

Why does issue automation fail when the GitHub issue template is missing?

Issue automation fails when the GitHub issue template is missing because enforced guard rails require specific issue fields and assignee data before any work begins. This validation prevents processing ambiguous or incomplete issue requests.