gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
81
92%
Does it follow best practices?
Impact
33%
1.00xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The workflow calls `scripts/inspect_pr_checks.py`, which uses the GitHub CLI to fetch PR check metadata and—critically—the GitHub Actions run/job logs (`gh run view <run_id> --log` and `gh api .../actions/jobs/<job_id>/logs`); those logs are outsider-authored content and are inserted into the agent-visible output as `logSnippet`/`Failure snippet`, which then becomes part of the LLM’s context when the agent summarizes and plans.
- Repository
- foryourhealth111-pixel/Vibe-Skills
- Commit
f627ab5
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.