claude-oss

Runs an open-source repo as its maintainer: triage, delegate, review, merge on green.

Install

/plugin marketplace add Digital-Process-Tools/claude-marketplace
/plugin install oss@dpt-plugins

Then run /reload-plugins, or restart Claude Code. Plugin registrations are read once at
session start, so a mid-session install leaves the agent registry unresolved until you do.

See docs/install.md for developing this plugin's own source, and for setting
up oss-workspace in a repo you maintain.

Type it once

/oss:run is what a session opens on, and the only thing a person normally types. It asks one
question — what does this repo need now — and answers it from state and config, never from an
argument. Each tick runs in a context discarded after it, so hours of running cost one tick.

flowchart TD
    YOU([you, once]) --> W["oss-workspace<br/>update plugin · wire channel · open session"]
    W -->|injects| RUN["/oss:run"]
    RUN --> DIAG["check the install and this repo<br/>repair what is ours, carry on"]
    DIAG -->|a gap that makes the loop unsafe| STOP([stop, and name what clears it])
    DIAG --> Q{"what does this<br/>repo need now?"}
    YOU -.->|when something looks wrong| DOC["/oss:doctor<br/>say what is wrong, start nothing"]
    Q -->|no config yet| CFG["probe the repo, write .oss.json"]
    Q -->|someone wrote to us| IN["inbound: issue · PR · comment"]
    Q -->|its trigger fired| REL["release: gates · audit · tag · publish"]
    Q -->|a backlog crossed its threshold| CUR["curate trap.d"]
    Q -->|a release just landed| TRI["triage the board"]
    Q -->|otherwise| BOARD["read the board, decide what is worth building<br/>one tick, in a context thrown away after it"]
    BOARD --> LANE["developer lane<br/>worktree · test first · self-review the diff · stops at a commit"]
    LANE --> PR["maintainer opens<br/>the pull request"]
    PR --> GREEN{"CI green and<br/>review passed?"}
    GREEN -->|no| LANE
    GREEN -->|yes| MERGE["merge"]
    CFG & IN & CUR & TRI & REL & MERGE --> RUN

The loop arms its own next turn and stops only on a direct instruction to stop.

The launcher

/oss:doctor prints the exact, paste-ready command to wire up oss-workspace for
the version you have installed. Run it from the repo you maintain.

More

• docs/overview.md — what it is for, and how to tell if work is inside that.
• docs/install.md — installing, developing it, the launcher and its symlink.
• docs/commands.md — every slash command.
• docs/status-line.md — every status-line field.
• docs/development.md — the test suite and this repo's own guards.
• docs/status.md — what installing this does and does not put in motion.
• docs/pick-the-work.md — how it decides what to build next.
• docs/open-the-workspace.md — what the launcher sets up.
• docs/autonomy.md — what "autonomous in someone else's repo" would take.
• CLAUDE.md — what is not proven yet, measured and dated at each release.

License

Community License — see LICENSE. Source-available, not open source: no commercial
redistribution, no competing use.

Built by Digital Process Tools in Toulouse, France.