- ticket-to-pr-loop.md 42 lines · 2.0 KB
Ticket-to-PR-Ready Loop
Loop Engineering — turn a backlog of issues into a steady stream of small, verified PRs without hand-holding each one.
🎯 Goal
Pick one actionable ticket, implement and verify the fix, and open a PR that a reviewer can approve quickly — then move to the next ticket.
⏱️ Schedule
Suggested interval: 30m.
▶️ Run it
/loop 30m "Take the next actionable open issue. Implement the fix in an isolated branch, add tests, verify, and open a conventional-commit PR linking the issue. If a ticket needs product decisions, label it for human review and skip. Continue until the queue is clear."🔁 Iteration steps
- Perceive — read the next open, actionable issue.
- Reason — confirm scope; if it needs human/product input, label and skip.
- Plan — outline the change and the test that proves it.
- Act — implement with
/fix-github-issue; commits followconventional-commits. - Observe — run tests; on green, open a PR with
/create-prthat links the issue.
🛑 Stopping condition
No actionable tickets remain — each is either a verified PR or flagged for human input.
🧩 Referenced components
command:git-workflow/fix-github-issue— implements the ticket fix.command:git-workflow/create-pr— opens the linked PR.hook:git/conventional-commits— enforces clean, conventional commit messages.
💡 Example
A "typo in error message" issue becomes a one-line fix with a snapshot test and a fix: correct auth error copy (#412) PR, all within a single pass.
Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-17
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector or how components are reviewed.