projectops weekly downloads statistics

<div align="center"> <img src="https://raw.githubusercontent.com/Cassiiopeia/projectops/main/docs/images/hero-en.webp" alt="Projectops: from issue to release" width="100%">

One install: issue → branch → release PR → deploy, with agent skills that drive each step.

한국어 | English | 简体中文 | 日本語

Status: actively maintained. npm latest is exactly what is on the main branch; work in progress on develop is never published. Versions can still ship several times a day. Note that npx projectops@<version> pins the installer only (workflow templates always come from the current main) (releases).

<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->

Latest version : v4.87.0 (2026-11-04)

View full version history

</div>

---

Get started in 30 seconds

I want to...	Run this
Start a new project	Click Use this template on GitHub (auto-setup in about a minute)
Add it to an existing project	npx projectops
Install Agent Skills only	npx projectops --mode skills
Check the install state (read-only)	npx projectops --mode doctor

You need Node.js 20.12+ and Git (Agent Skills also need Python 3). An interactive wizard runs with no separate install.

This is a real run on a sample Spring project (the wizard follows your system language, or use --lang en|ko). Version numbers shown were current when it was recorded. For non-interactive use and every option, see the CLI reference.

---

Why this template?

This project automates your development workflow on two axes.

① GitHub Actions: a develop-to-main release PR handles versioning and changelogs; merging it runs CI/CD deployment. ② Agent Skills: commands such as /pro-github, /pro-commit, and /pro-report let an AI agent drive each step of that automation for you: issues, commits in your own style, reports, and release PRs.

The usual way	With Projectops
Bump versions and create tags by hand	At release time the version is bumped from your commit titles and a tag is created
Write the changelog yourself	Generated for every release PR (commit analysis, or an AI summary if you add an AI key)
Set up CI/CD from scratch	Workflows for your project type, ready immediately
Format every issue by hand	/pro-github writes and files an issue from the standard template in one step
Copy the issue URL into commit messages	/pro-commit completes the message from the issue context, in your own style
Write PR descriptions and reports by hand	/pro-report analyzes the git diff and generates one
Re-type prompts for every code review or analysis	15 skills give consistent results without re-typing

---

Compared with other tools

If you only need one piece of this, a smaller tool may suit you better.

	projectops	release-please	semantic-release	changesets
Version decided from	Commit titles (feat → minor, feat! → major)	Conventional Commits	Conventional Commits (configurable)	Changeset files written in each PR
Review step before a release	A release PR (develop → main), merged automatically	A release PR you merge	None by default, releases on push	A "Version Packages" PR
Changelog	Written in the release PR (commit analysis, or an AI summary)	Generated	Generated (plugin)	Assembled from changeset files
CI/CD workflows for your project type	Yes (Spring, Flutter, React, Python; npm publish for Node)	No	No	No
Agent skills that run the cycle (issues, worktrees, commits in your style, reports, release PRs, real-device QA)	Yes	No	No	No
What it adds to your repo	About 60 files (below)	A workflow and a config file	A config file and a CI step	A .changeset/ folder and a CI step

• Want only versioning and a changelog? release-please or semantic-release is smaller.
• Publishing npm packages from a monorepo where each PR should say what changed? changesets fits better.
• Want the whole cycle (issue → branch → release PR → deploy) in one install, with agent skills on top? That is what projectops is for.

More in the full comparison.

Footprint, measured. With v4.84.0 on 2026-11-05, npx projectops --mode full --type basic --force in an empty repository added 56 files: 8 workflows, 30 helper scripts under .github/scripts/, issue, PR and discussion templates, version.yml and a setup guide. --type spring added 60 files (12 workflows).

---

What it actually looks like

Below is a real run, recorded after installing projectops in a sample repo in a test organization. The timer in the top right is real elapsed time; only the waiting parts are played back fast.

1. Open an issue and a branch name and commit message arrive automatically

When an issue is opened, GitHub Actions runs on its own and comments a branch name and a commit message template. Work on that branch name and the issue number links into your commits and reports automatically.…