ci-troubleshoot

ci-troubleshoot is a Build, CI & test failure triage skill for AI agents, published by BlackBeltTechnology in the pi-agent-dashboard repository on GitHub. Skillspace rates ci-troubleshoot C (78/100) and it passed the safety scan; the rating is based on static analysis only.

Diagnose failed GitHub Actions runs for pi-agent-dashboard. Maps the 6-workflow taxonomy (ci.yml, ci-electron.yml, _electron-build.yml, publish.yml, sync-release-version.yml, deploy-site.yml), walks the release pipeline (prepare→publish→electron→github-release with strict needs[] contract), surfaces known failure modes (lockfile mismatch, bad Node version, CHANGELOG already-versioned, npm publish ordering, no-bash-on-Windows lint, missing node-pty prebuilds, GO/NO-GO bundle-server guard), and shows how to read `gh run` logs and retrigger failed jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to understand which workflow does what. For triggering a release see `release-cut`; for revoking one see `release-revoke`.

Grade
C
Quality
78 / 100
Safety
Passed
GitHub stars
193

Unproven: rated by static analysis only, not yet compared head-to-head.

Our two independent classifiers differ on this skill's category, so treat the placement as provisional.

This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.

Our review

Architecture
96 / 100
Maturity
Structured: ships references or scripts
Security scan
No issues found
License
MIT
Adoption
Adopted by 0 other repositories, in 0 collections

Not checked yet

  • Not judged on the rubric yet (not a contender in its category)
  • No blind task eval yet
  • Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
  • Sibling files (scripts, references) not fetched; security scan covers SKILL.md only

Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.