Skip to content
Skills Library
Programming · Building & coding

github-issue-autofix

/github-issue-autofix

Implement a GitHub Issue fix on a branch and open a PR (Fixes #N). Use in conversation when the user gives an Issue number or URL and asks to implement or fix it. Also the L2 loop entry skill after autofix label, repository_dispatch, or workflow_dispatch. Interactive default is survey only; implement the fix when the request asks for changes to be made (for example fix, apply, or update) or automation sets agent_edit_allowed in Constraints. Detect skips when an open/draft PR already closes the Issue. Agent must not fire repository_dispatch.

Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
24
Scripts
10
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 10 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/detect_autofix.sh, scripts/lib/all.sh, scripts/lib/aws.sh, scripts/lib/common.sh, scripts/lib/csv.sh, scripts/lib/json.sh, scripts/lib/repo_paths.sh, scripts/lib/terraform.sh, scripts/lib/validation.sh, scripts/lib/yaml_map_order.py

What it does and when to use it

Implement a GitHub Issue fix on a branch and open a PR (Fixes #N). Use in conversation when the user gives an Issue number or URL and asks to implement or fix it. Also the L2 loop entry skill after autofix label, repository_dispatch, or workflow_dispatch. Interactive default is survey only; implement the fix when the request asks for changes to be made (for example fix, apply, or update) or automation sets agent_edit_allowed in Constraints. Detect skips when an open/draft PR already closes the Issue. Agent must not fire repository_dispatch.

Original author description

Implement a GitHub Issue fix on a branch and open a PR (Fixes #N). Use in conversation when the user gives an Issue number or URL and asks to implement or fix it. Also the L2 loop entry skill after autofix label, repository_dispatch, or workflow_dispatch. Interactive default is survey only; implement the fix when the request asks for changes to be made (for example fix, apply, or update) or automation sets agent_edit_allowed in Constraints. Detect skips when an open/draft PR already closes the Issue. Agent must not fire repository_dispatch.

How it works

  1. Input
  2. Output Specification
  3. Execution Scope
  4. Reference Files Guide
  5. Workflow
Original SKILL.md headings · 71 lines, 787 words
SKILL.md preview
---
name: github-issue-autofix
description: >-
  Implement a GitHub Issue fix on a branch and open a PR (Fixes #N). Use in
  conversation when the user gives an Issue number or URL and asks to
  implement or fix it. Also the L2 loop entry skill after autofix label,
  repository_dispatch, or workflow_dispatch. Interactive default is survey
  only; implement the fix when the request asks for changes to be made (for
  example fix, apply, or update) or automation sets agent_edit_allowed in
  Constraints. Detect skips when an open/draft PR already closes the Issue.
  Agent must not fire repository_dispatch.
license: Apache-2.0
metadata:
  author: y-miyazaki
  version: "0.1.2"
---

**UTILITY SKILL** — Issue→PR autofix on the branch caller (not entity observe).

## Input

- **Automation:** detect JSON from `detect_autofix.sh` with `result.issue_number`. Read `agent_edit_allowed` / `agent_edit_target` from `## Constraints`.
- **Interactive:** Issue number (or URL resolved to a number) plus optional failure context; there is no detect JSON. Read the Issue with read-only `gh issue view <n> --json number,title,body,state,labels,comments`. `agent_edit_allowed` follows the edit gate in Workflow: survey unless the request asks for changes to be made.

## Output Specification

Report per [common-output-format.md](references/common-output-format.md). On the automation path, follow [category-automation-envelope.md](references/category-automation-envelope.md). Apply shape: PR body includes the literal `Fixes #<N>`. Survey shape: reference the Issue as `Refs #<N>` and never use a closing keyword (`Fixes`, `Closes`, `Resolves`) — merging a survey PR must not close the Issue.

## Execution Scope

### USE FOR:

- Implement a minimal fix for the Issue on the integration branch worktree when `agent_edit_allowed: true`
- Synthesize PR body from `assets/pr-body-template.md` including `Fixes #<N>`

### DO NOT USE FOR:

- Issue triage labels/comments (github-issue-triage)
- PR revision from review comments (github-pr-revise)
- Calling `repository_dispatch` from the Agent

## Reference Files Guide

- [common-checklist.md](references/common-checklist.md) (always read)
- [common-output-format.md](references/common-output-format.md) (always read)
- [category-automation-envelope.md](references/category-automation-envelope.md) (read on automation path)
- [category-pr-body-links.md](references/category-pr-body-links.md) (read when synthesizing PR body)
- `assets/pr-body-template.md` (read when synthesizing apply PR body)
- `assets/pr-body-template-survey.md` (read when synthesizing survey PR body)

## Workflow

Resolve **agent_edit_allowed** before implementing:

| Source                                                                                                          | `agent_edit_allowed`                                                                                                                         |
| --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Interactive — default: the request asks to look, check, triage, or survey, or only names the skill              | `false` — survey only; do not edit files                                                                                                     |
| Interactive — the request asks for changes to be made (for example fix, apply, 修正して, 適用して, update, add) | `true` — implement the fix for the Issue                                                                                                     |
| Interactive — follow-up after a survey asking to apply                                                          | `true` — implement the surveyed fix candidates                                                                                               |
| Automation — `## Constraints`                                                                                   | `agent_edit_allowed: true` or `agent_edit_allowed: false` from [category-automation-envelope.md](references/category-automation-envelope.md) |

When intent is unclear, survey and offer to apply — edits are harder to undo than a report.

When `agent_edit_allowed` is `true`, resolve `agent_edit_target`: on the **interactive** path use `fix` (this skill); on the **automation** path read `agent_edit_target` from `## Constraints`. Do not branch on other caller metadata outside `## Constraints`.

**Delivery.** Interactive: leave edits in the working tree and report them; commit, push, or open a PR only when the user explicitly asks for that step, because those change shared state that other people see and cannot be quietly taken back. Automation: do not push or open a PR yourself; the caller delivers the branch and composes the PR body from your report.

1. Automation: read detect JSON; if `skip: true` or `status: error`, report the reason and stop. Interactive: resolve the Issue from the user's URL or number with `gh issue view`; if the Issue is closed, report that and stop. Check for an open or draft PR that already closes the Issue (for example `gh pr list --state open --search "<n> in:body"` and confirm a closing keyword for `#<n>` in its body); if one exists, report it as a skip and stop — same as the detect skip.
2. On the automation path, read [category-automation-envelope.md](references/category-automation-envelope.md) for Constraints and PR templates.
3. IF `agent_edit_allowed` is `false` → emit survey shape; load `assets/pr-body-template-survey.md` at synthesis when on automation path; stop.
4. ELSE IF `agent_edit_allowed` is `true` AND `agent_edit_target` is not `fix` → emit survey shape; note expected `agent_edit_target: fix`; stop.
5. ELSE IF `agent_edit_allowed` is `true` AND `agent_edit_target` is `fix` → implement the minimal fix for Issue `#N` on the worktree.
6. At synthesis, load the apply PR template; ensure body includes `Fixes #<N>` (interactive: the body is written for a PR the user asks you to open, or reported in chat).
7. Do **not** fire `repository_dispatch` or start other loops from the Agent.

### Error Handling

| Condition                                                 | Severity    | Action                                                          |
| --------------------------------------------------------- | ----------- | --------------------------------------------------------------- |
| Detect `status: error`                                    | Fatal       | Stop; do not mutate repository files                            |
| Detect `skip: true`                                       | Info        | Report skip reason; do not open a PR                            |
| Interactive: Issue is closed                              | Info        | Report that the Issue is closed; do not edit files or open a PR |
| Interactive: an open or draft PR already closes the Issue | Info        | Report it as a skip with the PR number; do not open another PR  |
| `agent_edit_allowed: false`                               | Info        | Survey only; do not edit files                                  |
| `agent_edit_target` not `fix` when edits expected         | Recoverable | Survey only; note mismatch in Overview                          |
| Validation tooling missing after edits                    | Recoverable | Defer in report; do not claim passing checks                    |
Files in this package (24)
  • SKILL.md 7 KB
  • eval.yaml 1 KB
  • assets/pr-body-template-survey.md 1 KB
  • assets/pr-body-template.md 1 KB
  • evals/tasks/github-issue-autofix-agent-edit-allowed-false.yaml 1 KB
  • evals/tasks/github-issue-autofix-automation-production-constraints.yaml 1 KB
  • evals/tasks/github-issue-autofix-basic.yaml 1 KB
  • evals/tasks/github-issue-autofix-interactive-check-stays-survey.yaml 1 KB
  • evals/tasks/github-issue-autofix-skip-open-pr.yaml 1 KB
  • evals/tasks/github-issue-autofix-trigger-negative.yaml 1 KB
  • references/category-automation-envelope.md 3 KB
  • references/category-pr-body-links.md 2 KB
  • references/common-checklist.md 1 KB
  • references/common-output-format.md 2 KB
  • scripts/detect_autofix.sh 25 KB
  • scripts/lib/all.sh 1 KB
  • scripts/lib/aws.sh 31 KB
  • scripts/lib/common.sh 9 KB
  • scripts/lib/csv.sh 4 KB
  • scripts/lib/json.sh 8 KB
  • scripts/lib/repo_paths.sh 16 KB
  • scripts/lib/terraform.sh 13 KB
  • scripts/lib/validation.sh 14 KB
  • scripts/lib/yaml_map_order.py 8 KB

Versions

RepositoryScoreLicence
This page · y-miyazaki/terraform-aws-base100Apache-2.0
y-miyazaki/terraform-aws-base90Apache-2.0

Database snapshot: 13.11.2026 · package version 2b33fe1b1b70 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100implement-issue
    Read a GitHub issue, create a branch, implement the solution, and open a PR. Use when given an issue number to implement.
  • 100solve-issue
    Solve a GitHub issue end-to-end and open a pull request. Use when the user wants to fix or resolve a specific GitHub issue (often by number or URL), or says "solve issue #123", "fix this issue", or "implement and PR this issue".
  • 100github-pr-revise
    Apply human PR review feedback to a pull request. Use in conversation when the user gives a PR URL or number plus the feedback to apply. Also the L2 loop entry skill on PR heads when detect finds the configured mention token. Interactive default is survey only; apply the…
  • 90work-on-issue
    Use when the user says "work on issue", "implement issue", "/work-on-issue", or asks to implement a GitHub issue end-to-end (not merely validate it). Takes an issue URL or number (defaults to the just-validated issue). Implements in an isolated worktree, verifies, commits,…
  • 84implement
    This skill should be used when the user asks to "implement an issue", "create a PR for issue", "implement issue #123", "turn this issue into code", or wants to implement a GitHub issue following an implementation plan and create a pull request.
  • 88fix-github-issue
    Fix a GitHub issue by number. Use when asked to fix GitHub issues.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.