skrrt-sh
- 7 skills
- 0 followers
- 6 hours ago last updated
- ▌ Pr · skrrt-sh bundlePush a branch and open or update its GitHub pull request or GitLab merge request. Use when the user asks to open a PR, or to create or update a merge request.
- ▌ Setup · skrrt-sh bundleConfigure this repository for the Skrrt ship workflows and select a branching strategy. Run once before commit, pr, and release.
- ▌ Commit · skrrt-sh bundleCreate focused conventional commits with a mandatory gitmoji. Use when the user asks to commit, write a commit message, or split changes into commits.
- ▌ Release · skrrt-sh bundleDraft, prepare, or publish a GitHub or GitLab release. Use when the user asks for release notes, wants to publish a release, or asks what changed since the last tag.
- ▌ Subagents · skrrt-sh bundleOrchestrate subagents to implement a multi-part scope — the main thread plans, briefs, dispatches, and reviews; strictly scoped subagents on Opus write the code. Use whenever the user asks for subagents, parallel or fan-out implementation, or handing work to agents, and for any plan with several independent parts they want done at once, even without the word subagent.
- ▌ Md Writer · skrrt-sh bundleWrite or edit knowledge-base Markdown with frontmatter, Mermaid diagrams, related-document links, and markdownlint validation. Use for guides, specs, ADRs, runbooks, and API documentation; not repository meta files such as README, CHANGELOG, CLAUDE.md, AGENTS.md, or SKILL.md.
- ▌ Self Documenting · skrrt-sh bundleKeep comments and documentation to the inevitable minimum so the code stays the single source of truth. Comments answer why, three lines at most; docs carry decisions and architecture, never how the system works; CLAUDE.md and AGENTS.md carry conventions, never situational facts; nothing points into the code by path, symbol, or line. Apply whenever writing or editing code, comments, docstrings, READMEs, design docs, CLAUDE.md, AGENTS.md, rules, or skills, even if the request never mentions documentation.