# logsnip: cut CI noise, keep the stack traces

> Source: <https://dev.to/sybilgambleyyu/logsnip-cut-ci-noise-keep-the-stack-traces-4cpi>
> Published: 2026-07-22 12:46:17+00:00

Cut the noise. Keep the stack traces.

CI logs are mostly package installs. The failure is a few dozen lines buried under thousands of `Downloading…`

lines. Scrolling for the real stack trace is a tax paid on every red build.

[logsnip](https://github.com/SybilGambleyyu/logsnip) is a zero-dependency Python CLI that extracts those failure regions and collapses the rest.

```
pip install git+https://github.com/SybilGambleyyu/logsnip.git
# or the whole toolkit:
curl -fsSL https://raw.githubusercontent.com/SybilGambleyyu/devkit/main/install.sh | bash
# Last failure from a GitHub Actions run
gh run view --log-failed | logsnip --last

# Headlines only
logsnip ci-full.log --summary

# Safe to paste into an AI assistant
gh run view --log-failed | logsnip --last | redactx
```

Built-in patterns cover pytest `E`

lines and `AssertionError`

, `npm ERR!`

, rustc `error[E…]`

, TypeScript `error TS…`

, GitHub Actions `##[error]`

, make failures, and common exit-code messages. Stack frames after a hit are pulled in automatically.

`--check`

exits 1 when error-like lines appear (CI gate)`--json`

for machines; `--summary`

for humans in a hurrySource: [github.com/SybilGambleyyu/logsnip](https://github.com/SybilGambleyyu/logsnip) · MIT