luan/pr-ci
skills/pr-ci/SKILL.md
Fix failing CI/GitHub Actions checks. Triggers: 'fix CI', 'fix GHA', 'build failing', 'tests failing in CI', 'checks red'.
$ install --global
skillsauthnpx skillsauth add luan/dot-claude pr-ciInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 1:09 PM9.9s1 file scanned
SKILL.md
- name:
- pr-ci
- description:
- Fix failing CI/GitHub Actions checks. Triggers: 'fix CI', 'fix GHA', 'build failing', 'tests failing in CI', 'checks red'.
- argument-hint:
- [--auto]
- user-invocable:
- true
- - "Bash(gh pr view:
- *)
- - "Bash(gh pr checks:
- *)
- - "Bash(gh pr list:
- *)
- - "Bash(gh run view:
- *)
- - "Bash(gh run list:
- *)
- - "Bash(gh repo view:
- *)
- - "Bash(git add:
- *)
- - "Bash(git commit:
- *)
- - "Bash(git push:
- *)
PR GHA Fixer
Fix failed GitHub Actions checks.
Safety: never rebases. Push requires confirmation (unless --auto).
Steps
-
Detect PR:
gh pr view --json number -q '.number'or ask user -
Verify branch (if PR specified manually)
-
Fetch failed checks:
gh pr checks <PR> --json name,state,bucket,link--auto→ fix all failed checks. Without--auto→ display as numbered list, ask "Which to fix?" -
Fetch logs:
gh run list --branch <BRANCH> --json databaseId,name,conclusion --limit 20 gh run view <RUN_ID> --log-failed -
Plan fixes: Identify root cause, create concise plan.
--auto→ proceed. Without--auto→ ask "Ready to execute?" -
Execute: Apply fixes, summarize changes.
-
Commit: Use
Skill(commit)to generate message and commit.--auto→ commit directly. Without--auto→ ask first. -
Push (optional):
--auto→ push automatically. Without--auto→ ask first. Detect stack tool:gh stack view --json 2>/dev/nullsucceeds →Skill(gh-stack:submit). Otherwisegt log --stack 2>/dev/nullsucceeds →Skill(gt:submit). Otherwisegit push.
Common Failures & Remediation
- Build — missing imports, type errors, syntax → read error output, fix source directly
- Test — outdated assertions, missing fixtures → update expectations or add missing test data
- Lint — formatting, unused imports/vars → run the project formatter, remove dead code
- Infra — secrets, rate limits, runner issues → can't fix locally; inform user to check repo/org settings
Related Skills
luan/sym
tools
VerifiedTrustedCommunity
Tree-sitter indexed code navigator (ct sym CLI). Use INSTEAD OF Read/Grep/Glob/Bash when exploring existing code, understanding how something works, locating a symbol, tracing the call graph up (impact) or down (trace), finding implementations of an interface, scoping a diff to one symbol, or preparing to edit code you have not read yet. Triggers: 'how does X work', 'explain this class/file/symbol', 'walk me through X', 'what does X do', 'where is X defined', 'who calls X', 'what does X call', 'find implementations of', 'what breaks if I change X', 'outline this file', 'map imports', 'show me this symbol', exploring unfamiliar repo, tracing call graph, scoping diff to a symbol, preparing to edit code I haven't read, about to Read a file over ~500 lines to understand it. Do NOT use for: writing new code from scratch, editing prose or config, running tests, or when a stack trace already names the file and line.
4SKILL.mdUpdated Apr 22, 2026
luan/vibe
development
VerifiedTrustedCommunity
Fully autonomous development workflow from prompt to commit. Chains spec → develop → review → commit. Triggers: /vibe, 'vibe this', 'autonomous workflow', 'just do it all', 'build this end-to-end', 'full pipeline', 'handle everything'.
4SKILL.mdUpdated Apr 21, 2026
luan/vault-sweep
development
VerifiedTrustedCommunity
Comprehensive vault maintenance — cross-references blueprints against codebase state to produce a maintenance plan: archive consumed artifacts, audit docs for staleness, propose new docs for undocumented stable systems. Triggers: 'vault sweep', 'sweep the vault', 'clean up vault', 'vault maintenance', 'what can we archive', 'audit blueprints', 'vault hygiene', 'blueprint cleanup'. Use whenever the user wants a holistic view of vault health rather than archiving a single artifact (that's /archive). Also use when the user asks what's stale, what needs docs, or whether artifacts can be cleaned up.
4SKILL.mdUpdated Apr 21, 2026
luan/test-plan
development
VerifiedTrustedCommunity
Analyze current diff, classify changes by risk, and produce structured manual test plan. Triggers: 'test plan', 'what should I test', 'manual testing', 'verification steps', 'QA checklist'. Exits early for trivial changes. Do NOT use when: writing automated tests — use /develop with TDD. Do NOT use when: reviewing code quality — use /crit instead.
4SKILL.mdUpdated Apr 21, 2026