Causefile Start beta

Local CI failure triage for GitHub Actions

Find the first useful cause in a failed CI run.

Causefile turns noisy Playwright, npm, typecheck, lint, and dependency failures into a cited likely cause, owner/file hint, and smallest next action.

Start beta See sample output Ask before paying
Tests
49/49 passing
Reviewed public rows
17/17 accepted
Hosted ingestion
None
Self-serve beta, manual delivery. Pay through Stripe, receive the local CLI, run it on your machine, return reviewed rows instead of raw logs.
ci-triage 
$ ci-triage triage playwright-flaky-test.log
Verdict: actionable
Likely cause: test_failure
Confidence: 0.95
Owner hint: tests/checkout.spec.ts:42
01 Log evidence

Playwright assertion timed out.

02 Cited cause

Button stayed disabled for 15000ms.

03 Next action

Inspect checkout fixture state.

Causefile report

Pay button never becomes enabled

  • Cause Playwright assertion timed out while waiting for the checkout button.
  • Cited lines `Expected: enabled`, `Received: disabled`, `Timeout: 15000ms`.
  • Next action Inspect the payment-ready fixture before changing app code.

Built for the first thirty minutes after red CI

A small local tool, not another platform rollout.

Cited diagnosis

Every report points to concrete log lines instead of summarizing the whole failure into vague prose.

Owner hints

File, package, and command hints tell the next person where to look first.

Review loop

Each run creates a row for `accepted`, `wrong`, or `needs_follow_up` so quality can be measured.

Sanitized sample

What the beta produces.

playwright-flaky-test.log 
1) tests/checkout.spec.ts:42:7 › checkout

Error: expect(locator).toBeEnabled() failed

Locator: getByRole('button', { name: 'Pay now' })
Expected: enabled
Received: disabled
Timeout: 15000ms

actionable · confidence 0.95

Likely cause: test failure

The log points to a failing Playwright assertion. Strongest owner hint: tests/checkout.spec.ts:42.

  1. Open the failing test and assertion.
  2. Confirm whether expected behavior or fixture data changed.
  3. Compare against the last merged change and dependency updates.

Privacy boundary

Private logs stay on your machine.

Local CLI only. No hosted log upload. No telemetry by default.

Reports are best-effort redacted, but generated artifacts should still be reviewed before sharing.

Support asks for safe excerpts or reviewed CSV rows, not raw private logs.

Contact before checkout

Ask for a sample review before buying.

If you want to confirm fit first, send a public failed GitHub Actions run, a safe redacted excerpt, or a question about install/privacy.

Email support@mgsoftware.dev

Paid private beta

EUR 299 for one team/repo, 30 days.

Includes the local CLI tarball, quickstart, one optional onboarding call, and email support for install, redaction concerns, and wrong triage reports.

  • Run the sample first.
  • Try 3-5 failed logs locally.
  • Return reviewed rows, not raw logs.
  • Refund if it cannot be installed or run in the first week.
Start beta Ask for a CI failure review