oss
v0.7.1Generic engineering practice, reusable in any repo (OSS or not): commit discipline, pull requests, stacked PRs, writing tests, technical writing, no-comments, GitHub issue creation, release notes, and scoped implementation and technical-writer agents. Depends on common.
By Cedric ZielLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 8 skill or MCP entries
- Source updated
- Sep 28, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install oss for Codex and Claude Code
codex plugin marketplace add cedricziel/claude-plugins
codex plugin marketplace upgrade cedricziel
codex plugin add oss@cedriczielPaste and run these commands in a terminal with Codex. They add and refresh the cedricziel catalog, then install this plugin.
Compatibility: the page URL and API slug “oss-3” remain stable.
- Codex:
oss-3@agent-plugin-marketplace→oss@cedricziel
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/cedricziel/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/oss/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/commit-discipline/SKILL.md├── skills/git-stacked-prs/SKILL.md├── skills/issue-create/SKILL.md├── skills/no-comments/SKILL.md├── skills/pull-request/SKILL.md├── skills/release-notes/SKILL.md├── skills/technical-writing/SKILL.md└── skills/writing-tests/SKILL.md
Included Skills8
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", "commit this", "open a PR", breaking down a feature, or any discussion of code changes or git operations.
Use this skill when breaking a large change into a stack of reviewable PRs with git on GitHub. Works in stages — evaluate changes, plan dependencies and ordering, execute the stack, then ship each PR through CI. Prefers GitHub's first-party `gh stack` (public preview) and falls back to native git (>= 2.38) + the gh CLI with no extra tools. Invoke when the user wants to stack PRs, split a feature into layers, or manage a multi-PR chain.
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 GitHub issue. DO NOT trigger on mentions of "issue" in passing, on bug reports the user is just describing without asking for a tracker entry, or on `/issue-run`'s own issue-triage/issue-resolve steps (those are separate workflows).
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
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 a branch is ready to go up for review.
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.
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.
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.
Plugin manifests2
{
"name": "oss",
"version": "0.7.1",
"description": "Generic engineering practice, reusable in any repo (OSS or not): commit discipline, pull requests, stacked PRs, writing tests, technical writing, no-comments, GitHub issue creation, release notes, and scoped implementation and technical-writer agents. Depends on common.",
"author": {
"name": "Cedric Ziel",
"url": "https://github.com/cedricziel"
},
"license": "MIT",
"repository": "https://github.com/cedricziel/claude-plugins",
"homepage": "https://github.com/cedricziel/claude-plugins",
"keywords": [
"oss",
"open-source",
"commit-discipline",
"pull-request",
"stacked-prs",
"testing",
"technical-writing",
"issue-create",
"release-notes",
"changelog"
],
"skills": "./skills/"
}{
"name": "oss",
"version": "0.7.1",
"description": "Generic engineering practice, reusable in any repo (OSS or not): commit discipline, pull requests, stacked PRs, writing tests, technical writing, no-comments, GitHub issue creation, release notes, and scoped implementation and technical-writer agents. Depends on common.",
"dependencies": [
"common",
{
"name": "coderabbit",
"marketplace": "claude-plugins-official"
}
],
"author": {
"name": "Cedric Ziel",
"url": "https://github.com/cedricziel"
},
"license": "MIT",
"repository": "https://github.com/cedricziel/claude-plugins",
"homepage": "https://github.com/cedricziel/claude-plugins",
"keywords": [
"oss",
"open-source",
"commit-discipline",
"pull-request",
"stacked-prs",
"testing",
"technical-writing",
"issue-create",
"release-notes",
"changelog"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[oss on Agent Plugins Marketplace](https://pluginsmp.com/plugins/oss-3)