Who it is forA developer with a backlog of small, well-described issues who wants draft changes checked before reading the diff.
The problemWriting and reviewing AI-generated changes by hand takes as long as writing them yourself, and it is easy to approve a diff that never ran its tests.
The outcomeA pull request that has a plan, a pass or fail review checklist citing file and line, and a stated test status, ready for your decision.
What you need first
- Python 3.12+
- uv
- git
- Node with npm, for the board build from source
- An Anthropic credential: an ANTHROPIC_API_KEY or a Claude subscription OAuth token from claude setup-token
- A git repository you want changed, and a GitHub or GitLab issue URL or a configured tracker
Steps
- Run
uv tool install no-human(orpipx install no-human). - Run
nh init && nh doctorto set the token, config, and first repo, then confirm the install works. - Run
nh startto open the board and worker on 127.0.0.1:8420. - Run
nh task add https://github.com/org/repo/issues/42 --repo ~/git/repowith your own issue and repo. - Run
nh reviewto read the reviewer's evidence checklist, thennh diffto see the change. - Run
nh approveto squash-land the pull request, ornh reject --reason "..."to send it back. (inferred, check the README)
Prompt for your agent
In the no_human repo, install the CLI, add the GitHub issue <issue-url> with --repo <local-repo-path>, and run nh review. Report the checklist items that failed with their file and line citations, and confirm whether the test status reads NOT RUN.
Caveat. The default install needs a configured model credential and a local repo, and the board build from source can take several minutes on a cold first install.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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