ci-failure-analyzer SKILL.md skillA
ci-failure-analyzer from pramoddutta/aitesterblueprint4x is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pramoddutta/aitesterblueprint4x/ci-failure-analyzer@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pramoddutta/aitesterblueprint4x
- Path
chapter_14_MCP_Create_VIBE/testskill-finder-mcp/skills/05-test-execution/ci-failure-analyzer/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 10, 2026
- Size
- 4,446 bytes
- Repository stars
- 14
- License
- none declared
Reads CI test results and classifies every failure as product bug, test bug, flaky, or environment, with the evidence behind each call. Use when an SDET says "why did the pipeline fail", "triage these CI failures", "is this a real bug or flaky", or pastes a JUnit XML, Allure, Playwright/Cypress report, or job log. Produces a triage table with confidence and next action per failure, a draft for human review before anything is filed.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# CI Failure Analyzer You turn a red pipeline into **a classified, evidence-backed failure list** so the team fixes the right thing first. Every label points to a log line, trace, or run history, never a hunch. ## When to use - A nightly or PR pipeline failed and someone needs to know what is real before stand-up. - A run has many failures and you suspect most share one root cause (env down, bad deploy). - A test "fails sometimes" and the team needs to decide: bug, flaky test, or broken env. ## Workflow 1. **Gather the artifacts.** Ask for the result file (JUnit XML, Allure results, Playwright or Cypress JSON/HTML report), the job log, the commit/build under test, and retry settings. If run history for the failing tests is available, ask for it too. Do not guess what a missing log would have said. 2. **Group by error signature.** Normalize each failure (exception type, message without ids or timestamps, top app frame) and cluster them. Ten failures with `ECONNREFUSED` in the same minute are one problem, not ten. 3. **Check retries and history.** Mark tests that passed on retry, and tests that both passed …
Read the whole file at its exact version.
How to install
mdr add pramoddutta/aitesterblueprint4x/ci-failure-analyzer@sha256:0402eb99d252c6d5The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6cqi24gme63cpo4z)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4446 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pramoddutta/aitesterblueprint4x · 14 stars · license none declared · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6cqi24gme63cpo4z GET https://markdownregistry.com/api/v1/resolve?ref=pramoddutta/aitesterblueprint4x/ci-failure-analyzer GET https://markdownregistry.com/api/v1/blob/0402eb99d252c6d56f78c2e210db73cf9bd4bc6a8fe7ad1e15b00da740fb0a65
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.