oss-ready-flow

Orchestrate a six-step OSS readiness workflow with per-step sub-agents and safety gates.

9|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Montimage/skills --skill oss-ready-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-ready-flow
Source: https://github.com/Montimage/skills/tree/main/skills/oss-ready-flow
Command: npx skills add https://github.com/Montimage/skills --skill oss-ready-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a six-step OSS readiness workflow to transform a private repository into an OSS-ready project.

Core Features & Use Cases

  • Executes a structured, multi-agent pipeline covering audit, branch cleanup, docs generation, README polishing, publications gathering, and an optional GitHub Pages landing page.
  • Writes per-step reports to the target repository under .oss-ready/, preserving restartability and auditability across sessions.
  • Enforces safety gates for destructive actions and requires explicit user approval for per-item changes, making OSS prep predictable and reviewable.

Quick Start

Run the OSS readiness flow on your repository to initiate the six-step prep process.

Frequently Asked Questions about oss-ready-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a private git repository for open-source release?

Preparing a private git repository for open-source release involves running a six-step OSS readiness workflow that audits the codebase, cleans branches, generates docs, polishes README files, gathers publications, and optionally creates a GitHub Pages landing page.

What is an OSS readiness workflow and what steps does it include?

An OSS readiness workflow is a structured multi-agent pipeline that transforms a private project into a public open-source repository through auditing, branch cleanup, documentation generation, README polishing, publications collection, and an optional GitHub Pages setup.

Do I need GitHub CLI to automate open-source repository preparation?

Yes, GitHub CLI access is required for remote actions during open-source repository preparation. The workflow also requires a git repository with at least one commit and the oss-ready skill installed to execute its six-step pipeline.

Can I review changes before my repository is made open-source?

Yes, the workflow enforces safety gates and requires explicit user approval for per-item modifications. It shows diffs without committing, ensuring your open-source repository preparation remains predictable and fully reviewable.

How does the open-source preparation workflow track progress across sessions?

The open-source preparation workflow tracks progress by writing per-step reports to the target repository under the .oss-ready directory, preserving restartability and auditability across sessions for the multi-agent pipeline.

What are the limitations of automating open-source project readiness?

A limitation of automating open-source project readiness is that destructive actions require explicit safety gates and user approval. Additionally, the workflow requires a git repository with at least one commit and will not commit changes automatically without review.