Oss Launch

Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / co

16 stars 8 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add AnayDhawan/oss-launch --skill oss-launch

Manual install

git clone --depth 1 https://github.com/AnayDhawan/oss-launch.git /tmp/oss-launch
mkdir -p ~/.claude/skills
cp -r /tmp/oss-launch/. ~/.claude/skills/oss-launch

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# oss-launch

Turn a repo into a credible open-source project: scan what exists, fill the gaps with
adapted (not boilerplate) files, then optionally launch it.

`templates/` holds the payload this skill writes into a USER's repo. The root files
(README, LICENSE, etc.) describe oss-launch itself. Never confuse the two.

## Run (when invoked)

Work top to bottom. Do not dump all files blindly; scan first, then fill only real gaps.

**0. Scan the repo** (details: `references/scan.md`)
- Stack: `package.json` / `pyproject.toml` / `Cargo.toml` / `go.mod` / `composer.json` /
  `*.csproj` / `Gemfile` / `pom.xml` or `build.gradle` / `Package.swift` -> language,
  package manager, test/build/lint commands. Full marker table: `references/scan.md`.
- Existing OSS files present vs missing: README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT,
  SECURITY, CHANGELOG, `.gitignore`, `.github/` templates, CI workflows.
- Git: `git remote -v` -> `{{OWNER}}/{{REPO}}` + default branch. `gh repo view` -> public?
- Declared license (`package.json` "license" field / existing `LICENSE`).
- Demo asset present? (screenshot / gif in README or `docs/`).
- **Secret + brand-leak scan** (do this every time, even private->public):
  `.env`, API keys, tokens, hardcoded absolute/personal paths, internal-only references.
  If anything leaks, STOP and surface it before generating or publishing anything.

**1. Report** the findings and a gap table. Run the audit for the checklist:
```bash
bash scripts/audit.sh .
```

Read the full skill on GitHub

Details

Skill name: oss-launch
Repository: AnayDhawan/oss-launch
Repo updated: 23 September 2026

FAQ

What does the Oss Launch skill do?

How do I install the Oss Launch skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add AnayDhawan/oss-launch --skill oss-launch. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Oss Launch popular?

It lives in AnayDhawan/oss-launch, which has 16 GitHub stars and 8 forks.

Related skills

Github Stars Curator

Leexunhuan743/github-stars-curator

Organize starred GitHub repos into stable, clear lists: detect new stars, download READMEs into a local corpus, classify each repo against the taxonomy, and sync the approved mapping back to GitHub via gh. Use this when a user wants their starred repos sorted into lists, a recent batch of new stars filed incrementally, or their star-list taxonomy reviewed and refined. Do not use for general GitHub issue/PR management, repo code search, or bookmarking non-GitHub resources.

Git & Code Review

Remote Computer

paoloanzn/remote-computer

Configure and provision a remote development VM on AWS EC2 or Google Cloud Compute Engine, or a local SSH-ready Linux development container with apple/container on an Apple silicon Mac. Verify provider context, size the machine (host-aware container resource suggestions and Dockerfile configurations saved under ~/Documents/Containers), create dedicated VM-access SSH keys, optionally discover and port local Git/GitHub/GPG configuration with shared GitHub authentication keys, maintain the ~/.vms.json live-VM registry, reconcile status, and prepare direct SSH access. Use when a user asks to creat

Git & Code Review

Repo to Skill

shuyhere/repo-to-skill

Generate an agent skill from a GitHub open-source repository. Use when asked to create a skill from a repo URL, turn a GitHub project into a usable skill, or generate skill files for a CLI/library/framework. Triggers on phrases like "create a skill from this repo", "make a skill for vllm", "turn this GitHub project into a skill", "generate a skill from repo". Also use when asked to "skillify" a tool or generate usage instructions from source code. Command usage — `/skill repo-to-skill <github-repo-url>`.

Git & Code Review

Irpf Brasil

Danielbluz/skill-irpf-brasil

Assistente especializado em Imposto de Renda Pessoa Física (IRPF) Brasil — ciclo 2026, ano-base 2025. Use quando o usuário mencionar "IRPF", "Imposto de Renda", "declaração de IR", "malha fina", "DARF", "REVAR", "Cashback IRPF", "pré-preenchida", "Núcleo Familiar", "restituição IR", "bets imposto", "ComprovaBet", "e-Social IR", "DIRF", "ganhos bolsa imposto", "day trade", "GCAP", "ganho de capital", "vender imóvel", "isenção 180 dias", "MEI declaração", "lucro distribuído", "espólio inventário herança", "saída definitiva exterior", "residência fiscal", "IRPFM", "imposto mínimo", "Lei 15.270",

Git & Code Review

Github Demand Radar

geekjourneyx/github-demand-radar

Use when the user asks to analyze a GitHub repository's issues/PRs to identify high-value commercial demand opportunities. Triggers: 「扫issue」「扫PR」「找需求」「分析仓库」「找商业化点子」「独立开发者切入点」「需求雷达」「扫一下明星项目」「生成需求报告」. Outputs scored demand cards with JTBD analysis, RICE scoring, Ugly Workaround evidence, and fake-door probe drafts. Also works in PR scan mode (Phase 1B) to find rejected/stale PRs as market gap signals.

Git & Code Review

Git Ship

oil-oil/git-ship

自动化 Git 工作流一键发布助手，执行完整的「ship」流程：基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。调用 ship 本身就是对完整流程的授权；自动推断分支名、commit message 和 PR 内容，并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败，持续修复和重试，直到改动成功合并。不要因可自行修复的失败暂停，只在认证、权限、仓库保护等无法由当前环境解决的外部阻塞出现时请求用户介入。仅在用户明确表达「ship」意图时触发，例如： - 直接说「ship」「/ship」「git ship」 - 明确要求完整走完 git 流程：「帮我走一遍 git 流程」「拉 main、切分支、提 PR、合并」 - 使用类似「发布这次改动」「把这些改动提成 PR 并合并」的表达不应触发的情况： - 只是想 commit - 只是想创建 PR - 只是想 push 代码 - 讨论 git 相关问题或解释 git 概念

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.