Repowise (@repowisedev) header
Repowise (@repowisedev) profile picture

Repowise

@repowisedev

Your coding agent knows the codebase before it touches it. Fewer wrong edits, fewer wasted tokens. Open source, runs on your machine.

repowise.dev
Joined June 2026
  • Tweets112
  • Following66
  • Followers39
21Media
Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)Photo by Repowise (@repowisedev)
repowise 0.59 is out: 251 PRs in 4 days from 37 contributors, 26 of them first-timers. · guided setup for a new repo · a System Map of how your services call each other · Salesforce and COBOL, mapped end to end · agents record the decision each commit made pip install -U repowise Link: github.com/repowise-dev/repo…
2
5
127
Your agent says a function has zero callers and opens a PR to delete it. Before you merge, here are the 3 places a grep never looks and how to check each one:
1
1
3
124
more replies
3. Time. Some callers only run monthly or at year-end. Run git log -S on the name to find the commit that added it and read why. If that commit mentions an incident, leave it alone until you know the story.
1
3
7
Zero callers is a lead. The history is the alibi. Repowise shows agents dead code markers next to the 'why' history, so they read both before they delete anything.
3
10
Your agent says a function has zero callers and opens a PR to delete it. Before you merge, here are the 3 places a grep never looks and how to check each one:
1
1
3
91
more replies
2. Outside the repo. Crontabs, Terraform, Helm values, another team's service, a notebook someone runs by hand. If it's an HTTP handler or public API, check the access logs first.
1
3
5
3. Time. Some callers only run monthly or at year-end. Run git log -S on the name to find the commit that added it and read why. If that commit mentions an incident, leave it alone until you know the story.
2
3
Your agent says a function has zero callers and opens a PR to delete it. Before you merge, here are the 3 places a grep never looks and how to check each one:
1
1
3
102
more replies
2. Outside the repo. Crontabs, Terraform, Helm values, another team's service, a notebook someone runs by hand. If it's an HTTP handler or public API, check the access logs first.
1
3
7
3. Time. Some callers only run monthly or at year-end. Run git log -S on the name to find the commit that added it and read why. If that commit mentions an incident, leave it alone until you know the story.
2
5
2. Block instead of polling. gh pr checks --watch (or gh run watch --exit-status) waits until the run ends and exits non-zero on failure. One tool call instead of a wake-up every minute.
1
2
7
3. On red, read only what broke. gh run view <run-id> --log-failed | tail -n 100 shows the failing step's output without twenty minutes of dependency install.
2
5
1. Check the status and skip the logs. gh pr checks gives pass/fail/pending for each job. In AGENTS.md or CLAUDE.md: check CI with gh pr checks, read logs only when a job failed.
1
1
3
15
If your agent waits for CI by re-reading the whole build log every time it checks, these are the 3 gh commands to give it instead.
1
1
2
75
Asked the agent to harden a function. Most of the diff guards against inputs that can't happen. Ask these 3 questions before you accept any of those guards:
1
1
2
56
more replies
2. Where does the data come in? Validation belongs at the boundary: request handler, queue consumer, CLI parser. One check at the edge beats five checks three layers deep.
1
2
3
3. Has this failure ever happened? Search logs and incident notes for the error the guard prevents. If it never fired, weigh it against everyone who has to read past it every day.
2
4
Load more