yeet
Skill1 starsChanged 38 days agoNo licenceView on GitHub
Quick-ship session work: fetch origin/main into local main, merge origin/main into local dev, commit leftover session files if needed, push origin/dev, open PR main ← dev, rebase-merge immediately with --admin (do not re-push dev after merge just to carry the merge commit). Watch the GitHub/Vercel build of the ship SHA until Ready or Error (do not merge / do not claim complete on Error). After that production build is Ready, watch the PR for Codex and other review-agent comments and fix P0–P2 with a follow-up ship. Apply additive production migrations when the ship includes them; stop and ask on destructive schema. The wcp issue file is already the close record. After origin/dev, record the dev SHA in that repo's Notion issues database. When the production build of origin/main is Ready, set Status done. Do not call Linear. Use when the user runs /yeet or says "yeet it". Do not use for /prb, "push dev and PR to main", "ship it", babysit, or careful CI-watched merges — those stay /prb.
- Reads credentials
- Commits and pushes
15 other projects use a version of this.
Adopted by
Most recently taken up by
- TidalPaladin/skillstheir own version, first seen Nov 8, 2026
- PaulRBerg/dot-agentstheir own version, first seen Nov 6, 2026
- PaulRBerg/agent-skillstheir own version, first seen Oct 24, 2026
- kriegcloud/beep-effecttheir own version, first seen Oct 8, 2026
- leaf76/agent-skillstheir own version, first seen Aug 17, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
Used with
Projects with it also use interview-me, codebase-design and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
seikaikyoSkillinterview-me
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 3 projects that use this
GoogleSkillcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 4 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- openai/skills★ 27ksame name
- JetBrains/skills★ 386same name
- PaulRBerg/agent-skills★ 104same name
- kriegcloud/beep-effect★ 78same name
- EnzeD/skills★ 9same name
- PaulRBerg/dot-agents★ 6same name
- Adhamxon/claude-code-skills★ 2same name
- FuSheng-MG/Pi-Agent-skills★ 1same name
- lyh843/AgentSkills★ 1same name
- misty-step/laboratory★ 1same name
5 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 repository18 other files it gives its agents.
- agent-onboard-promptSkill
- deep-secSkill
- execute-planSkill
- human-copySkill
- identifySkill
- implementSkill
- issueSkill
- issuesSkill
- mapSkill
- prbSkill
- project-reviewSkill
- solveSkill
- startSkill
- statSkill
- tidySkill
- vercel-flagsSkill
- walkSkill
- water-cooler-protocolSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. 0 are common, 9 are distinctive, and 21 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
21
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 15 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.

