registry/skills/gha-diagnosis/SKILL.md
Use when GitHub Actions checks fail, workflow runs are red, or user asks to fix CI. Triggers on "fix CI", "actions failing", "checks are red", "pipeline broke", "workflow failed". User may provide a run URL, job ID, or just ask to fix.
npx skillsauth add provectus/awos-recruitment gha-diagnosisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fetch failed workflow logs via gh, diagnose root causes, fix, verify locally, commit. All failures in one pass.
User may provide:
gh run list --status failure --limit 5https://github.com/org/repo/actions/runs/123 → extract run IDgh run view <id> --log-failedRead .github/workflows/*.yml to understand the exact commands each job runs. These are your local verify commands.
gh run view <run-id> --log-failed
Group failures by root cause:
| Category | Signals | Typical Fix | |----------|---------|-------------| | Lint/Format | linter, formatter errors | Auto-fix or targeted edit | | Test | assertion errors, crashes | Fix code or test | | Security | vulnerability flags | Upgrade dep, scoped override | | Stale workflow | action SHA mismatch, deprecated syntax | Update workflow YAML | | Env/secrets | missing var, auth failure | Fix workflow env block | | Build | type errors, import failures | Fix source or dependency | | Spec drift | generated code stale | Regenerate artifacts |
Process in dependency order: workflow config → lint → tests → build.
gh run list --limit 1 --json status,conclusion,url| Pitfall | Instead |
|---------|---------|
| Guess fix from job name | Read gh run view <id> --log-failed |
| Blanket dep override | Scope to specific dependency paths |
| Update action SHA blindly | Check release notes for breaking changes |
| Fix warnings not in the error | Only fix what CI flagged |
| --no-verify to bypass hooks | Fix the hook issue |
development
Insurance underwriting domain knowledge for building automated submission processing systems. Covers submission-to-bind lifecycle, document extraction patterns, compliance gates (sanctions, licensing, clearance), human-in-the-loop design for regulated financial services, confidence calibration for extracted fields, operating mode progression (manual to automated), and evidence traceability requirements. Use when designing or implementing underwriting pipelines, extraction agents, compliance workflows, HITL review systems, or decision package assembly for insurance or MGA operations.
development
This skill should be used when the user asks to "write TypeScript code", "create a TypeScript module", "define TypeScript types", "add type annotations", "use generics", "handle errors in TypeScript", "set up tsconfig", "organize TypeScript project", or when writing any TypeScript code that is not tied to a specific library or framework. Covers type system, strict mode, naming conventions, error handling, async patterns, and project structure.
development
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions. Enforces Provectus opinionated conventions (exact version pinning, etc.) on top of community best practices.
development
This skill should be used when the user asks to "write Swift code", "create a Swift type", "set up a Swift package", "review Swift code", "refactor Swift", "use async/await in Swift", "fix Swift style", or when generating any Swift source code regardless of target platform. Provides modern Swift 6+ best practices covering type system, optionals, concurrency, error handling, protocols, generics, and idiomatic patterns. Does not cover any specific platform or framework.