DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to shorten test and lint output so an agent reads only failures with Reslop

Wrap npm test and lint commands with Reslop so agents get failures and a short summary, not passing noise.

Who it is forA developer who runs tests and lint through an AI agent and finds long passing output wastes context and hides the real errors.

The problemFull test and lint logs are long, and the failing lines are easy to miss for both people and agents.

The outcomeA Markdown report of failures and diagnostics, with the raw log saved next to it for the agent to read when needed.

What you need first

  • Node.js >=18.15.0 and npm
  • git installed, with the repository you want to review cloned locally
  • Windows Terminal if you are on Windows
  • An ACP-capable agent command on PATH, such as claude-agent-acp or codex-acp, if you want to run a plan in an agent

Steps

  1. Run npm i -g reslop once to install the tool.
  2. Edit the scripts in package.json so each program is prefixed with reslop t -- and steps are joined with &&, for example "test": "reslop t -- npm run -s lint && reslop t -- node --test".
  3. Run npm test in the repository. (inferred, check the README)
  4. Open the report saved in .log/ and check that it lists failures and a summary without passing results.

Prompt for your agent

In the repository at <repo-path>, run `npm test` and read the reduced report that reslop saves in .log/. Report each failure with its file and the raw log path. Verify that passing results are absent from the report and that the raw file in .log/ exists.

Caveat. The README says the reduced report groups similar problems, but it does not show an example of the output, so compare it with the raw log on your first run.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page