/loop Process every open category-theory issue into passing pull requests
Process all open issues in this repository using the following loop:
- Select one open issue that has no unresolved dependencies and is ready to be worked on.
- Work on only one issue at a time.
- Use the wiggum skill to manage the research, planning, implementation, verification, and review required for the issue.
- You may create a workflow and delegate tasks to subagents, but no more than two subagents may execute concurrently.
- Complete and verify all work associated with the selected issue.
- Create and push a pull request containing all changes required to resolve the issue. Reference the issue in the pull request description, so that GitHub will automatically close it when the PR is merged.
- Use the fix-ci skill to ensure that every CI check for the pull request passes.
- Once the pull request is complete and all CI checks are green, begin the next iteration with another eligible open issue.
Continue until every open issue has a corresponding pull request that will resolve it when merged.
Some issues may depend on others. In those cases, create stacked pull requests: base each dependent issue’s pull request on the pull request for its dependency. The resulting pull-request dependency tree should mirror the issue dependency tree. Do not begin an issue until all its dependencies have corresponding completed, CI-passing pull requests.
If work is interrupted by a temporary service limitation—for example, provider overload, token exhaustion, or a required waiting period—check whether service is available again once per hour. When service resumes, continue from exactly where you stopped.
The task is complete only when every open issue has a corresponding pull request and every pull request passes all CI checks. The pull requests should then be mergeable in dependency order so that merging all of them closes every issue.
For each issue you work on, create a new Git worktree and branch, and in that worktree run de so that you can later use direnv exec . $COMMAND to run rocq and other tools. Each PR gets its own worktree and branch, so that I can return to that worktree later if I need to make any further changes myself.
As you loop, implementing these issues, I want you to add another task at the beginning of each loop: Take the lowest numbered open PR in the project that is passing CI and merge it, then wait to ensure that the master branch passes CI before moving on to implement your issue. If master fails CI, fix that first, then continue the original purpose of the loop to resolve GitHub issues one by one until they are finished. In this way, we should "merge a PR make a PR".