Builtby Win Skills
builtby-win-skills is a Claude Code plugin for the Build phase that automates GitHub issue, branch, PR, and coordination workflows across seven bundled skills.
by builtby-win · github.com/builtby-win/skills
Automate GitHub issue pickup, parallel worktrees, PR flow, and closure rituals so Claude Code stays aligned with how you ship on GitHub.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install builtby-win-skills@builtby-win/skillsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:builtby-win/skills") and the paste-ready config with skillselion.get_install_config("plugin:builtby-win/skills").
What it does
builtby-win-skills is a Claude Code plugin marketplace entry that packages seven GitHub-centric automation skills for builders who live in issues, branches, and pull requests. It targets indie developers and small teams who want the agent to manage backlog selection, spin up isolated worktrees, drive implementation against an issue, and finish with merge confirmation and housekeeping instead of ad-hoc git reminders. The keywords point at concrete rituals—create branches, manage parallel work, sqlite-backed snapshots, draft PRs, and post-ship learnings—so the bundle reads less like a generic git cheat sheet and more like an opinionated ship loop. Install it when Claude Code is your daily pair programmer on GitHub and you want repeatable commands for starting work, staying on the right branch, and closing the loop when something is merged. It complements native git tooling rather than replacing CI; think coordination glue for solo builders who still own every hat from triage to release notes.
Highlights
- Seven bundled skills covering GitHub issues, branching, PRs, and team-style coordination from one Claude Code plugin
- Parallel worktree and branch workflows for starting work without stalling the main line
- Backlog and dashboard-oriented helpers (including SQLite snapshot patterns in keywords) for what is in flight
- Draft-to-done closure steps: confirm merge, capture learnings, and clean branches after ship
- Blog and publish-oriented keywords for tying shipped work to content updates when you document releases
Why builders use it
Solo builders lose hours context-switching between GitHub issues, local branches, worktrees, and half-finished PRs while Claude drifts off the ticket you meant to ship.
After you add the plugin, Claude can follow repeatable GitHub rituals from issue selection through merge confirmation and branch cleanup without you re-explaining your process each session.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is builtby-win-skills for?
It is for Claude Code users who manage product work in GitHub and want agent skills for issues, branches, PRs, and parallel worktrees instead of manual git hygiene.
When should I use builtby-win-skills?
Use it whenever you start a ticket, need isolated branches or worktrees, or want structured closure after a PR merges—including learnings and cleanup.
How do I add builtby-win-skills to my agent?
Install the builtby-win/skills Claude Code plugin from the Skillselion catalog entry, register the marketplace in Claude Code, and invoke the bundled skills by name when working on GitHub-backed tasks.
Comments
Share how you use builtby-win-skills, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.