SkillsAdd

oxsecurity/megalinter

fix-issue

End-to-end workflow to fix a GitHub issue — collect context, analyze, implement on a branch, open a PR, then hand off to /pr-watch-fix until CI is green.

First seen Jun 21, 2026

Installation

$ npx skills add oxsecurity/megalinter --skill fix-issue
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from oxsecurity/megalinter · top by installs.

npx skills add oxsecurity/megalinter
megalinter-fix 55 megalinter-setup 53 megalinter-check 53 megalinter 53 analyze 4 pr-watch-fix-renovate 3 pr-watch-fix 3 test 3 add-linter 3 renovate-rebase 3

Browse all from oxsecurity/megalinter

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.6K
License LICENSE
Default branch main
Open issues 25
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash Read Grep Glob Edit Write AskUserQuestion WebFetch WebSearch
Declared agents claude-code
More metadata
internal
1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,255 B
  • docs SUMMARY.md 172 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

Resolve the GitHub issue $ARGUMENTS end-to-end.

Delegation hints (token / model optimisation):
- Build step: delegate make megalinter-build runs to the build-runner agent (haiku).
- Version pin edits: delegate to version-bumper (haiku).
- CI watching after PR open: hand off to the pr-watch-fix skill (sonnet), which itself delegates polling to pr-monitor (haiku).
- Security-related issues: delegate CVE analysis to security-analyst (opus) — but you're already on opus, so do it inline if cheaper.

Global git/PR rules (no AI attribution, commit-as-user, no pushes to main, no --force, stage by path) live in CLAUDE.md → Git & PR Conventions. Follow them — do not restate them here.

Step 1 — Resolve the issue

Parse $ARGUMENTS (accept 123, #123, owner/repo#123, full URL). If empty, ask the user.

gh issue view <ref> --json number,title,body,labels,state,url,author,comments

Read body and all comments in full — context often lives in a comment. If the issue is closed, ask before proceeding.

Step 2 — Gather context

  • Linked PRs / prior attempts: gh issue view <n> --json closedByPullRequestsReferences,timelineItems
  • Grep for any file paths, error strings, linter names, descriptor IDs, env vars mentioned in the issue
  • Read the relevant descriptor (megalinter/descriptors/), subclass (megalinter/linters/), reporter (megalinter/reporters/), or fixtures (.automation/test/)
  • Fetch external links with WebFetch — upstream release notes often contain the fix

Step 3 — Analyze and propose

Form a concrete hypothesis. Ask via AskUserQuestion when any of these are true:

  • Root cause is ambiguous and you have more than one plausible explanation
  • Multiple valid fix approaches with real tradeoffs (descriptor vs. subclass, version bump vs. behavior patch, rename vs. alias)
  • The fix touches user-visible behavior (config keys, defaults, output format, env-var semantics)
  • It's a feature request whose design isn't already implied by the issue
  • You can't reproduce the bug from the description

Present: failing behavior, hypothesis, 2–3 options, recommendation. Include a "stop and let me investigate" option when the cause is unclear.

Skip the question only when the fix is local and obvious.

Step 4 — Prepare the branch

CURRENT_BRANCH="$(git branch --show-current)"
DEFAULT_BRANCH="$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name)"

If CURRENT_BRANCH equals the default branch (main/master/etc.), create fix/issue-<NUMBER>-<short-slug> off it. Otherwise keep working on the current branch.

If git status --short shows unrelated uncommitted changes, stop and ask.

Step 5 — Implement

  • Descriptor changes → edit YAML, then make megalinter-build (NEVER make megalinter-build-with-doc)
  • Python → see .claude/rules/python-style.md
  • Never edit files marked @generated by .automation/build.py — change the source and rebuild
  • Do NOT update CHANGELOG.md for CVE ignores or version bumps; for genuine user-facing fixes, add one line under Fixes in the beta section, written for end users per .claude/rules/changelog.md (what changes for them — no implementation details)
  • Run quick local validation (python -m py_compile, etc.) — Docker-only checks are left to CI

Step 6 — Commit

Match the repo's commit style (git log --oneline -10). Format:

<type>: <imperative one-line summary> (#<ISSUE_NUMBER>)

<optional body, 1–3 lines>

Fixes #<ISSUE_NUMBER>

Use a HEREDOC:

git commit -m "$(cat <<'EOF'
fix: <summary> (#<N>)

<body>

Fixes #<N>
EOF
)"

Step 7 — Push and open the PR

HEAD_BRANCH="$(git branch --show-current)"
BASE_BRANCH="$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name)"
git push -u origin "$HEAD_BRANCH"

Pass --base and --head explicitly so gh never prompts and never picks the wrong target (especially with forks):

gh pr create --base "$BASE_BRANCH" --head "$HEAD_BRANCH" --title "<title>" --body "$(cat <<'EOF'
## Summary

<2–4 sentences: root cause and how this PR fixes it>

## Changes

- <bullet per meaningful change>

## Test plan

- [ ] <how to verify>
- [ ] <edge cases>

Fixes <ISSUE_URL>
EOF
)"

Capture the PR number and URL.

Step 8 — Hand off to /pr-watch-fix

Invoke /pr-watch-fix. It owns the 5-minute polling loop, log inspection, fix-commit-push cycle, bot-rebase handling, and stop conditions.

One nuance to apply before invoking: CI-fix commits should use Refs #<N> (not Fixes #<N>) so a later squash-merge of a follow-up doesn't prematurely close the issue.

When /pr-watch-fix returns, report one line:

  • Success: PR #<N> is green: <url>
  • Stuck: Stuck on <check>: <root cause>. PR: <url>. Need your input.