oss

Plugin oss from marketplace cedricziel in cedricziel/claude-plugins. Commands read from the repo's manifest — 4 days ago.

Skills (9)

• commit-discipline

  Enforces atomic commit discipline and fast PR cycles to keep the main branch always shippable. Use proactively when planning a feature, breaking work into tasks, making any code changes, staging files, writing commit messages, or discussing what to ship. Triggers on: "let's add X", "I'm working on Y

• git-stacked-prs

  Use this skill when breaking a large change into a stack of reviewable PRs

• issue-create

  Create a well-structured, actionable GitHub issue from context the user gives you — picks the right template (bug/feature/docs/task/question), gathers the details that template needs, and files it with `gh issue create`. TRIGGER ONLY on `/issue-create <context>`, or an explicit ask to create/file a

• no-comments

  Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

• pull-request

  Defines the required shape for a pull request's title and body. ALWAYS use this skill when opening a pull request, drafting a PR description, or writing a PR title — not optional. Triggers on: "open a PR", "draft the PR description", "write the PR title", "create a pull request", or any point where

• release-notes

  Use when drafting, rewriting, or reviewing release notes or a changelog entry for a GitHub release or tag, when an auto-generated or release-please release body needs to become readable, or when asked what changed between two versions for the people who use the software.

• skill-maintenance

  What makes an agent-skill change worth keeping, and how a skill is laid out: when to add, edit, or delete a skill, which scope it belongs in, how to write the description, and where references and scripts live and how SKILL.md links them. Use whenever you are about to create, edit, or remove a skill

• technical-writing

  Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

• writing-tests

  Principles for writing good tests, distilled from the TDD canon (Beck, Fowler, Meszaros, Freeman & Pryce, Cooper). Use whenever writing new tests, reviewing test code, doing TDD red-green-refactor, or deciding what and how to test — unit, integration, or end-to-end, in any language.

Subagents (3)

• coder

  Implements a well-scoped coding task end to end — feature, bug fix, refactor, or test — in whatever language the repo uses. Delegate to it whenever the work is "write/change code and make it pass", so the orchestrator stays free for planning, review, and integration. Not for open-ended investigation

• comment-sicko

  A deranged comment-hater that savors deletion and condemns workaround code.

• technical-writer

  Writes or rewrites user-facing prose — readme, guide, reference page, RFC, release notes — applying the `technical-writing` standard (Diátaxis, Google developer style, STE, Global English) and `unslop`. Delegate whenever the deliverable is documentation rather than code, so the orchestrator stays fr

Hooks (1)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/scripts/session-start.sh"

Similar plugins