Implement Issue

What it does

When your agent uses it

• Issue details are provided in the prompt and the agent should produce the repository diff and a concise implementation summary
• Without creating commits
• Pull requests itself unless a cloud workflow explicitly asks for it

Example prompts

• “/implement-issue”

Requirements

• Python 3

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

1. 1Start from the shared implement-specs behavior. Treat approved spec material as the source of truth for behavior and implementation shape.
2. 2Read the issue details carefully. Review spec_context.md first when it exists. For the issue description and prior discussion, run python…
3. 3Inspect the repository to understand the current implementation before making changes.
4. 4Implement the requested behavior in the checked-out branch, keeping the changes scoped to the issue and aligned with any approved spec…
5. 5Keep specs aligned with implementation. If the checked-out branch contains corresponding spec files under specs/GH/ and the implementation…
6. 6Do not let unresolved issue comments silently override approved spec context. If a comment suggests a different direction than the…
7. 7Do not include issue number references (e.g. (#N), Refs #N) in commit messages. The issue is already linked in the PR body, the branch…
8. 8Run the most relevant validation available in the repository for the files you changed. Prefer existing build, test, lint, or typecheck…
9. 9Write a concise markdown summary for the workflow to reuse in implementation_summary.md at the repository root. Include what changed, how…
10. 10If the prompt asks for it, write pr-metadata.json at the repository root containing the structured PR metadata described in the Inputs…
11. 11Treat spec_context.md, implementation_summary.md, and pr-metadata.json as temporary workflow files only. Do not include them in the final…
12. 12Default behavior: do not stage files, create commits, push branches, open pull requests, or use the GitHub CLI. If the prompt explicitly…

What it can do on your machine

Read from SKILL.md and the folder at commit a2bb45f. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • python
  • gh

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implement Issue loads about 2k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 1,011 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~102

When it runs · the whole SKILL.md, loaded when a task matches

~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from warpdotdev/oz-for-oss at commit a2bb45f, republished under its MIT licence (© warpdotdev). 1,011 words, ~1,995 tokens.

name

implement-issue

description

Implement a GitHub issue in this repository by applying the shared `implement-specs` workflow with Oz-specific issue, spec-context, and summary-file handling. Use when issue details are provided in the prompt and the agent should produce the repository diff and a concise implementation summary, without creating commits or pull requests itself unless a cloud workflow explicitly asks for it.

python .agents/shared/scripts/fetch_github_context.py --repo OWNER/REPO issue --number N
python .agents/shared/scripts/fetch_github_context.py --repo OWNER/REPO pr --number N [--include-diff]
python .agents/shared/scripts/fetch_github_context.py --repo OWNER/REPO pr-diff --number N

{
  "branch_name": "oz-agent/implement-issue-42-add-retry-logic",
  "pr_title": "fix: add retry logic for transient API failures",
  "pr_summary": "Closes #42\n\n## Summary\n..."
}

© warpdotdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/implement-issue of warpdotdev/oz-for-oss.

Open the folder on GitHubat commit a2bb45f