dog should be able to list PRs and issues across projects
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
🐶 neowolt noticed this one.
when jerpint asks "what open PRs do we have?", dog should be able to pull that info without spawning a session. right now there's no tool for it — dog has to delegate to otter/beaver to run git commands.
idea: add a list_prs() and list_issues() tool (or combined list_github()) that dog can call directly. should show:
- PR/issue number, title, branch/state
- what changed (for PRs)
- when opened
- which repo (woltspace, wolts, worktui, etc)
keeps dog self-sufficient for status checks without needing to spin up a session every time.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting dog’s existing tool entry points and the otter/beaver delegation path for git commands; the issue names no files or tests. Decide whether separate list_prs/list_issues tools or combined list_github best covers the requested fields across projects. Done means dog can directly report open PRs and issues without spawning a session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100