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; apply when the user explicitly requests a fix or may_edit is true. Detect skips when an open/draft PR already closes the Issue. Agent must not fire repository_dispatch.

Licence
Apache-2.0
Last repository change
18.10.2026

Assessment and security

90/ 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.
Content25 / 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
23
Scripts
10
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.10.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; apply when the user explicitly requests a fix or may_edit is true. 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; apply when the user explicitly requests a fix or may_edit is true. 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 · 64 lines, 469 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;
  apply when the user explicitly requests a fix or may_edit is true. 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 `may_edit` / `write_target` from `## Constraints`.
- **Interactive:** Issue number (or URL resolved to a number) plus optional failure context; same Constraints defaults as automation survey unless the user explicitly requests a fix.

## 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). PR body must include `Fixes #<N>`.

## Execution Scope

### USE FOR:

- Implement a minimal fix for the Issue on the integration branch worktree when `may_edit: 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 **may_edit** before implementing:

| Source                              | `may_edit`                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Interactive — default               | `false` — survey only; do not edit files                                                                                 |
| Interactive — explicit fix language | `true` — user asks to implement/fix the Issue in the same request                                                        |
| Automation — `## Constraints`       | `may_edit: true` or `may_edit: false` from [category-automation-envelope.md](references/category-automation-envelope.md) |

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

1. Read detect JSON; if `skip: true`, report skip reason and stop.
2. On the automation path, read [category-automation-envelope.md](references/category-automation-envelope.md) for Constraints and PR templates.
3. IF `may_edit` is `false` → emit survey shape; load `assets/pr-body-template-survey.md` at synthesis when on automation path; stop.
4. ELSE IF `may_edit` is `true` AND `write_target` is not `fix` → emit survey shape; note expected `write_target: fix`; stop.
5. ELSE IF `may_edit` is `true` AND `write_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>`.
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         |
| `may_edit: false`                            | Info        | Survey only; do not edit files               |
| `write_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 (23)
  • SKILL.md 5 KB
  • eval.yaml 1 KB
  • assets/pr-body-template-survey.md 1 KB
  • assets/pr-body-template.md 1 KB
  • evals/tasks/automation-production-constraints.yaml 1 KB
  • evals/tasks/basic.yaml 1 KB
  • evals/tasks/may-edit-false.yaml 1 KB
  • evals/tasks/skip-open-pr.yaml 1 KB
  • evals/tasks/trigger-negative.yaml 1 KB
  • references/category-automation-envelope.md 3 KB
  • references/category-pr-body-links.md 1 KB
  • references/common-checklist.md 1 KB
  • references/common-output-format.md 2 KB
  • scripts/detect_autofix.sh 8 KB
  • scripts/lib/all.sh 1 KB
  • scripts/lib/aws.sh 29 KB
  • scripts/lib/common.sh 9 KB
  • scripts/lib/csv.sh 4 KB
  • scripts/lib/json.sh 8 KB
  • scripts/lib/repo_paths.sh 15 KB
  • scripts/lib/terraform.sh 13 KB
  • scripts/lib/validation.sh 14 KB
  • scripts/lib/yaml_map_order.py 6 KB

Versions

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

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 9588a5750762 (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.
  • 100github-fix-issue
    Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission. Use whenever the user mentions fixing a GitHub issue, says "fix issue #123", "work on this issue", "修复 issue", or references a GitHub issue number or URL.
  • 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".
  • 100implement
    Use when the user wants an existing GitHub issue turned into a finished, reviewed pull request — "implement issue 123", "pick up ticket 45", "build the feature described in issue 7", "go fix the bug in issue 99", "start working on that issue". Triggers on any request to do the…
  • 90github-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 a configured mention (@loop). Interactive default is survey; apply when the user…
  • 100git-issue
    GitHub issue to PR end-to-end — branch, TDD implementation, PR — one issue or several in parallel. Use when asked to work on an issue, fix issue #N, or batch-process several.

Feedback and reports

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