fix-issue-github 100/100

Is fix-issue-github safe to install?

SaferSkills independently audited fix-issue-github (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/fix-issue-github/SKILL.md · 1 file

skills/fix-issue-github/SKILL.md1.7 KB · Markdown

description: Read a GitHub issue and apply code changes to resolve it.

argument-hint: "[issue-number]"

disable-model-invocation: true

Read a GitHub issue and apply code changes to resolve it.

$ARGUMENTS is the issue number. If $ARGUMENTS is empty, ask the user to provide an issue number and stop.

Steps:

Check that gh is installed and authenticated by running gh auth status. If not, tell the user and stop.
Run gh issue view $ARGUMENTS --json title,body,comments,labels to fetch the issue details. If the issue doesn't exist or is already closed, tell the user and stop.
Analyse the issue:

Read the title and body to understand what is being requested or what is broken.
Read any comments for clarifications, additional context, or decisions already made.
Identify whether this is a bug fix, feature addition, or documentation change.

Explore the codebase to find the relevant files:

Search for symbols, filenames, or patterns mentioned in the issue.
Read the relevant files to understand the current implementation before making any changes.

Apply the minimum code changes needed to resolve the issue:

Fix bugs by correcting the root cause, not just the symptom.
Add features by following the existing patterns and conventions in the codebase.
Do not refactor or change code unrelated to the issue.
Do not add comments, docstrings, or logging unless the issue specifically asks for it.

After making changes, summarise what was changed and why, referencing specific files and line numbers. Ask the user to review the changes before committing.
Do not commit or push — leave that to the user.

$ARGUMENTS

fix-issue-github— agent skill

Is fix-issue-github safe to install?

Audit the pieces. Scan the whole. Decide.