implement-issue

Orchestrate issue-to-diff translation using local shared implementation skills.

292|39|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill implement-issue-warpdotdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-issue
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/implement-issue
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill implement-issue-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement issue-to-diff translation by orchestrating the local shared implement-specs workflow with Oz-specific issue, spec-context, and summary handling. Use when issue details are provided and the agent should produce the repository diff and a concise implementation summary without creating commits or PRs unless a cloud workflow explicitly asks for it.

Core Features & Use Cases

  • Thin Oz wrapper around local shared skills: implement-specs and spec-driven-implementation to drive behavior consistently.
  • Handles inputs from GitHub issues: issue metadata, optional spec_context.md, and optional issue_comments.txt, with output in a dedicated implementation_summary.md.
  • Produces deterministic outputs: repository diff/patch, plus a structured pr-metadata.json when requested, and a concise summary for PR docs.
  • Reuses the fetch_github_context script to pull on-demand context without inlining untrusted bodies.

Quick Start

Provide the issue details and run the implement-issue workflow to generate the repository diff and a concise implementation summary.

Frequently Asked Questions about implement-issue

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

FAQPage Schema
How do I automate GitHub issue implementation to generate a repository diff?

To automate GitHub issue implementation, provide the issue details and run the workflow to generate a repository diff and a concise implementation summary. It translates issue metadata into code changes without creating commits unless requested.

What inputs are needed to convert a GitHub issue into a code diff?

Converting a GitHub issue into a code diff requires issue metadata as the primary input. It also optionally supports spec_context.md and issue_comments.txt to provide additional context for generating the patch and implementation_summary.md.

Does the issue-to-diff workflow create pull requests automatically?

The issue-to-diff workflow does not automatically create commits or pull requests. It outputs a repository patch, a concise summary, and optional pr-metadata.json with branch naming support for separate PR workflows.

How does the automated issue implementation workflow handle untrusted GitHub context?

The automated issue implementation workflow handles untrusted GitHub context by reusing the fetch_github_context script. This pulls on-demand context dynamically without inlining untrusted bodies directly into the implementation process.

What is the best way to generate structured PR metadata from a single GitHub issue?

The best way to generate structured PR metadata from a single GitHub issue is using an orchestration workflow that produces deterministic outputs. It generates a structured pr-metadata.json alongside the repository diff for single-issue engineering tasks.