brunnojob/devrescue

What it does

DevRescue reads build, runtime and CI logs and isolates recognizable failures by signature. For each group it shows redacted evidence, any available file and line references, likely causes, and commands you can review. A separate diagnosis view accepts source excerpts you supply and produces stack-specific hints and a step-by-step repair plan. You can also compare two logs, maintain a manual checklist, export Markdown or JSON, and keep optional browser history.

The project ships three surfaces: a React/Vite workbench on GitHub Pages (open the workbench), a dependency-free Node.js CLI, and a GitHub Action. Analysis is deterministic and signature-based; the tool does not execute the commands it suggests.

Quick start

For the CLI, use Node.js 22 or newer and run from the repository root:

git clone https://github.com/brunnojob/devrescue.git
cd devrescue
node bin/devrescue.js analyze examples/build.log --markdown
node bin/devrescue.js analyze examples/build.log --json
node bin/devrescue.js doctor .

The first two commands print a report for the sample log; --markdown and --json choose the output format. doctor checks the repository setup and offers a narrowly scoped, reviewed .env ignore fix.

For the web app:

git clone https://github.com/brunnojob/devrescue.git
cd devrescue/apps/web
npm ci
npm run dev

Use /devrescue/ locally. Account features need a public VITE_API_BASE_URL set in a private .env.local; the API itself is built and started separately with npm run api:build && npm run api:start (local development steps).

GitHub Action

The action analyzes a log file that already exists in the job; it does not download job logs. Create ci.log in an earlier step, then:

- uses: actions/checkout@v4
- name: Analyze an existing log
  if: always()
  uses: brunnojob/devrescue@main # Pin a reviewed commit SHA in production.
  with:
    log-path: ./ci.log
    fail-on-findings: 'false'

Sanitized Markdown is written to the job summary. The action supports Linux, Windows and macOS, including the older Bash on macOS (action example).

Constraints

Redaction is pattern-based, so review every report before sharing or uploading it. The root CLI and the web app's browser analyzer are both signature-based but maintained separately, so their findings can differ. The hosted account service requires the Azure runtime settings, direct GitHub OAuth credentials and OIDC deployment authorization described in the Azure setup guide; a green build does not verify a live database, and no paid Azure resource is created automatically.

Azure sync is opt-in and uploads only a reviewed derived report to PostgreSQL; full raw logs stay local. Account access keeps a three-hour trial tied to a verified GitHub identity, with sponsor access for monthly or confirmed one-time support, while the source and local CLI remain MIT licensed. Real Azure connectivity must be tested separately from the PGlite-based test suite. See the published limitations and security documents.

HotRepo's take

The project entered HotRepo's new-project chart for TypeScript on 2026-11-15 with 112 stars, adding 12 stars during the roughly 1.5-hour measured window; forks stayed at zero. That is a very short observation window with no earlier ranking history, so the data shows a brief burst of attention, not adoption or retention. The most concrete technical distinction in the repository is the split between the root CLI/action engine and the newer browser analyzer, which the README itself says may produce different findings; for anyone evaluating the output, which surface produced a report matters as much as the report itself.