ship-feature
Skill327 starsChanged 3 days agoLicence not identifiedView on GitHub
Autonomously ship a feature end-to-end with zero human intervention: plan it, implement it, review it with a team of subagents, boot the full stack, drive it in a real browser like a user (agent-browser + the driving-gaia skill), capture before/after screenshots, open a PR to master, and drive CI and CodeRabbit to green. Use this skill whenever the user asks to "ship" a feature, "one-shot" a feature, build something "end to end", implement something "autonomously", take an idea "from spec to PR", or asks for a complete feature with PR, screenshots, and passing CI — even if they don't name this skill. Also use it when a cloud session is handed a feature request and expected to deliver a finished, verified PR without a human in the loop. Do not use it when the user just wants code written or an ordinary PR without the full verified-shipping pipeline (live E2E, screenshots, drive-to-green).
- Reads credentials
- Commits and pushes
16 other projects use a version of this.
Adopted by
Most recently taken up by
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- seanmcgary/claude-skillstheir own version, first seen Nov 11, 2026
- babs/skillstheir own version, first seen Nov 8, 2026
- azents/azentstheir own version, first seen Oct 23, 2026
- mergewatch/mergewatch.aitheir own version, first seen Oct 18, 2026
- shubham303/meelu-analytics-mcptheir own version, first seen Oct 13, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- classroomio/classroomio★ 1.7ksame name
- hoangsonww/Claude-Code-Agent-Monitor★ 1.2ksame name
- ultimo-rs/ultimo★ 777same name
- AmineDjeghri/awesome-os-setup★ 682same name
- seldonframe/seldonframe★ 40same name
- mergewatch/mergewatch.ai★ 26same name
- azents/azents★ 16same name
- shubham303/meelu-analytics-mcp★ 9same name
- babs/skills★ 4same name
- FAHTHIZ/oasis★ 4same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository133 other files it gives its agents.
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- accurate-testingSkill
- adaptSkill
- agentation-self-drivingSkill
- animateSkill
- auditSkill
- audit-websiteSkill
- backlink-analyzerSkill
- biome-gritql-pluginsSkill
- bolderSkill
- ci-to-greenSkill
- clarifySkill
- colorizeSkill
- copywritingSkill
- creating-design-systemsSkill
- critiqueSkill
- Debug IssueSkill
- delightSkill
- distillSkill
- driving-gaiaSkill
- emilkowal-animationsSkill
- executing-plansSkill
- Explore CodebaseSkill
- find-skillsSkill
- gh-stackSkill
- impeccableSkill
- landing-page-copywriterSkill
- layoutSkill
- logging-best-practicesSkill
- make-interfaces-feel-betterSkill
- mintlifySkill
- motionSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- optimizeSkill
- overdriveSkill
- parallel-worktreesSkill
- performanceSkill
- polishSkill
- PR Image EmbeddingSkill
- programmatic-seoSkill
- pytest-coverageSkill
- python-testing-patternsSkill
- quieterSkill
- react-doctorSkill
- reading-gaia-logsSkill
- reading-stream-recordingsSkill
- receiving-code-reviewSkill
- Refactor SafelySkill
- requesting-code-reviewSkill
- Review ChangesSkill
- seo-auditSkill
- seo-geoSkill
- shapeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

