English | 简体中文

Issue Finder finds GitHub issues worth handing to coding agents, prepares local context, and stops before code changes.

cargo install issue-finder

If you want your main coding agent to handle first-run setup, give it this prompt:

Install cargo issue-finder locally, run `issue-finder profile bootstrap --json`,
review the report's tech stack, keyword, and project evidence, remove noise,
then update `[profile]` in `~/.issue-finder/config.toml`. Do not copy session
bodies, secrets, system prompts, or tool output into the config. Then run
`issue-finder doctor` and `issue-finder scout --limit 10` to verify.

Then configure GitHub access and check local readiness:

export GITHUB_TOKEN="$(gh auth token)"
issue-finder init
issue-finder doctor

Find candidates and prepare a handoff:

issue-finder scout --limit 10
issue-finder scout --repo owner/repo --limit 10
issue-finder prepare owner/repo#123
issue-finder handoff <inbox-id> --print

Issue Finder writes local state under ~/.issue-finder by default. Use ISSUE_FINDER_HOME=/tmp/issue-finder-demo for isolated runs.

Issue Finder also exposes a JSON tool contract for coding agents:

issue-finder tools list
issue-finder tools call issue-finder.scout --arguments '{"limit":10}'
issue-finder tools call issue-finder.scout --arguments '{"repo":"owner/repo","limit":10}'

• Usage guide
• Agent-safe preparation runtime
• Safe probes
• Repository guidance for coding agents

cargo test
cargo clippy --all-targets -- -D warnings
cargo fmt --all

This repository is licensed under the MIT License.