Loading...
Loading...
Found 38 Skills
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
End-to-end open-source contribution for Agent/LLM projects: discover GitHub repos (stars, downloads/usage, recent commits, issue close ratio, PR merge speed, release cadence) and rewrite each project description in the user's language (what it does, problem, scenarios), analyze an Agent/LLM repo, write a scoped PR plan, implement it, open a GitHub PR, then write a PR summary from saved artifacts. Use when the user wants to search for contributable projects, find open source projects, Agent open source, MCP/LangChain repositories, star 1000, GitHub repo search; pastes a GitHub URL for open source contribution analysis, PR direction, good first issue, Agent architecture flaws; asks for technical solution, implement the plan, submit PR with feat/fix/refactor/test/docs; or produce PR summary, summary.md, review submitted PR, pastes a pull request URL / previously mentioned project. Trigger even without the word skill. Do not use for private product feature work or non-Agent general OSS drive-bys.
Take finished work in tester-army/e2e to a PR a human can review without fighting CI or bots - checks, verification against the built packages, a fresh-context self-review, the PR itself, then babysitting to the Ready for Human Review label. Use whenever you are asked to open, create, ship, or submit a PR, or when implementation is done and the next step is review.
The worker's router in a repository run by the Boring Factory. Use at the start of every task from a work packet (a task issue, its acceptance lines and their proof): it picks the playbook, the principles and the proof the pull request must carry. Adapted from pstack's poteto-mode.
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.
Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix, re-review) until nothing is left to fix, applying ALL fixes on the PR branch, wait for CI green, then squash-merge. Use when asked to "ship it", "ship PR
The skill to revert unnecessary changes and leave only essential changes when a user requests a cleanup of changes, or before committing and creating a pull request.
Build an effort by orchestrating sub-agents, and deliver a pull request. Use when asked to build or orchestrate an effort from its spec and tickets.
Open a draft PR and work through the user's review comments. Once ready for review, explain feedback and wait for direction. Trigger on "yeet".
Pick up an effort from a handoff document and orchestrate it to a pull request.
Use for the full bug-fix pipeline only on explicit request. Never infer from an ordinary bug fix. Runs the compressed pipeline.