Skip to main content
Jeden Skill in Manus ausführen
mit einem Klick
GitHub-Repository

coach-ship-skills

coach-ship-skills enthält 6 gesammelte Skills von leighstillard, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.

gesammelte Skills
6
Stars
2
aktualisiert
2026-06-22
Forks
0
Berufsabdeckung
2 Berufskategorien · 100% klassifiziert
Repository-Explorer

Skills in diesem Repository

babysit
Softwareentwickler

Shepherd an open PR to merge. Watches CI, fixes failures, addresses review comments, resolves conflicts, and enables/executes merge when green. Use after opening a PR, when the user says babysit/watch/get this merged, or as the final step of /ship.

2026-06-22
design-check
Softwareentwickler

Visual and UX review for user-visible changes: frontend components, HTML/CSS, templates, dashboards, rendered docs, emails, and CLI output formatting. Use as part of /ship when a diff touches UI/human-facing output. If nothing user-visible changed, explicitly mark not applicable and stop.

2026-06-22
pr
Softwareentwickler

Commit, push, and open a pull request for the current change. Use when the user says open a PR, ship this, commit and push, or as the PR creation step of /ship. Requires verification evidence in the PR body.

2026-06-22
ship
Softwareentwickler

Take a finished local change to a merged PR through non-negotiable release gates. Use when the user says ship it, /ship, get this merged, release this, or when /coach has a READY local diff. Enforces simplify, verify, design applicability, PR evidence, independent review, CI, and merge babysitting while preserving Anthropic budget where safe.

2026-06-22
simplify
Softwareentwickler

Simplify a completed diff before it ships. Use before /ship, after a feature works, or when a change feels over-engineered. Removes unnecessary abstraction, scope creep, dead code introduced by the diff, and confusing structure without changing behaviour.

2026-06-22
verify
Softwarequalitätssicherungsanalysten und -tester

Prove a change actually works before it ships. Use whenever a change is done, after implementing a feature/fix, before opening a PR, or when the user says verify/check this works/is this actually working. Tests passing is not sufficient; this skill requires real entry-point evidence.

2026-06-22