projectops

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. To stay on a version you have tested, run npx projectops@<version> (releases).

Latest version : v4.52.1 (2026-10-16)

View full version history

Get started in 30 seconds

You only need Node.js 20.12+. 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: one push to main handles versioning, changelogs, and 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.

Compared with other tools

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

• 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.

Footprint, measured. With v4.36.2 on 2026-10-08, npx projectops --mode full --type basic --force in an empty repository added 52 files: 8 workflows, 26 helper scripts under .github/scripts/, issue, PR and discussion templates, version.yml and a setup guide. --type spring added 56 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.

Drive it from your agent: /pro-github files the issue, /pro-init-worktree sets up the workspace, and /pro-commit writes the commit in your format.

2. Open a PR and a change summary arrives automatically

Open a PR from a work branch and a change summary built from the commits is posted as a comment. Push more commits and the same comment is updated instead of piling up new ones.

Drive it from your agent: /pro-report analyzes the diff and posts the implementation report; /pro-agent-test verifies the change by actually running it.

3. Open a release PR and everything from versioning to merge and tag is automatic

Open a PR from the development branch to main and it writes the release notes, decides the version from commit titles (feat, fix, ...) and puts it in the PR title, merges automatically, and creates the version tag. This example had feat commits, so the minor version went up.

Drive it from your agent: /pro-changelog-deploy pushes develop and opens the release PR for you.

The warning banner GitHub shows for Korean branch names is hidden in the recording. Everything else is the unedited screen.

Make it yours

Skills write in your style. Put your preferences in ~/.projectops/config/config.json; nothing is asked on first run.

{
  "preferences": { "language": "en", "tone": "short and direct", "rules": ["no emoji"] },
  "skills": { "pro-commit": { "preset": "gitmoji" } }
}

Team formats in version.yml win; your tone still applies. Details: Skills guide.

Example: /pro-oss-consult on this repo

We ran /pro-oss-consult on this repo, then fixed what it found (measured 2026-10-13).

What it changed: descriptions were cut to short English triggers, a shared contract test now checks every skill, and pro-commit follows your team's version.yml commit template.

What is inside

🔄 Development cycle automation

📊 Analysis (no code changes)

🔧 Implementation (writes real code)

Design, planning, and implementation are handled by superpowers (brainstorming → writing-plans → executing-plans), not by this plugin.

📝 Documents and artifacts

Extras (optional plugin): /pro-architecture-consult (keep AI-written code maintainable: audit, refactor one item at a time, check each diff, freeze violations), /pro-synology-expose — claude plugin install projectops-extras@projectops-marketplace --scope user

AI development cycle

Agent Skills cover the entire development cycle.

flowchart TD
    A(["Start work"]) --> B["/pro-github<br/>File an issue"]
    B --> C["/pro-init-worktree<br/>worktree + copy sensitive files"]
    C --> D{"Type of work"}

    D -->|New feature / design / refactor| E1["superpowers:brainstorming<br/>Decide what and why"]
    D -->|Bug / outage| E2["superpowers:systematic-debugging<br/>Find the root cause"]

    E1 --> P["superpowers:writing-plans<br/>Implementation plan"]
    P --> F["superpowers:executing-plans<br/>Run the plan"]
    E2 --> F
    F --> H["/pro-review<br/>Self-review"]
    H --> I["/pro-commit<br/>Issue-linked commit"]
    I --> J["/pro-report<br/>Implementation report + GitHub comment"]
    J --> K(["Open PR"])
    K --> L["/pro-changelog-deploy<br/>Release PR + automerge"]

Full list of Skills and usage: docs/en/skills.md

GitHub Actions pipeline

flowchart TD
    A([Push to develop]) --> B[Integrate]
    B --> C[develop→main release PR]
    C --> D["Finalize version in the PR<br/>commit-based bump + tag + AI changelog"]
    D --> E[Auto-merge]
    E --> F["Push to main → CI/CD deploy<br/>Flutter / Spring / React, etc."]
    F --> G([Done])

# Claude Code
claude plugin marketplace add Cassiiopeia/projectops
claude plugin install projectops@projectops-marketplace --scope user

# Gemini CLI
gemini extensions install https://github.com/Cassiiopeia/projectops

# Codex CLI (macOS / Linux)
codex plugin marketplace add Cassiiopeia/projectops

The --mode skills wizard registers the Codex marketplace and also prepares the native skills fallback. Use /plugins only to check or manage the install.

Where the Codex plugin marketplace is unavailable, use the fallback install described in the Skills guide.

# Cursor / the full Agent Skills install menu (recommended: npx)
npx projectops --mode skills

Claude Code prefers /pro- autocomplete, Gemini prefers its extension, and Codex prefers its plugin marketplace. See the Skills guide for details.

Supported project types

Comment commands

Run automation by commenting on an issue or PR.

Details: PR Preview | Flutter builds | Issue automation

Setup

Personal access token (optional)

Everything runs with the built-in GITHUB_TOKEN. Add a personal access token as the repository secret _GITHUB_PAT_TOKEN only if you need one of these:

Without a token, workflows that should run after a release merge are started with an explicit dispatch, so you do not need a token for that.

A fine-grained token with Contents, Pull requests, Issues and Workflows set to Read and write should cover the first row. We have not verified fine-grained tokens end to end yet; for Projects sync we have only tested a classic token. If a fine-grained token fails, please open an issue.

Repository Settings → Secrets → Actions → New repository secret
Name: _GITHUB_PAT_TOKEN

Organization settings

Settings → Actions → General
├─ ✅ Allow GitHub Actions to create and approve pull requests
└─ ✅ Read and write permissions

Things to know

We would rather tell you up front when this is not a fit.

• GitHub only. It assumes GitHub Actions and GitHub issues/PRs, so GitLab and others are not supported.
• Releases assume a develop branch → default branch PR flow. Branch names can be changed in version.yml, but it does not suit a repo that does not use two branches.
• A personal access token is optional. You need one only to merge past branch protection or to sync a Projects board. See Setup.
• It adds about 50 files to your repository (workflows, helper scripts, templates). See the measurement.
• New versions ship often. latest follows every push to main with no delay. Pin a version you have tested with npx projectops@<version>.
• Server deploy workflows assume a Docker server reachable over SSH.

Documentation

Browse and search everything on the docs site. The main guides are in English. A few wizard pages are still Korean only (translations are welcome, see #799).

• Getting started
• CLI reference
• Agent Skills guide
• Versioning
• Changelog automation
• PR Preview
• Issue automation
• SSH + Docker deploy
• Flutter CI/CD
• Troubleshooting

Support

• Issues: bug reports and feature requests
  • Finished issues are marked with the status: done label and closed automatically when a release is merged (close_on_release).
• CONTRIBUTING.md: contribution guide
• ARCHITECTURE.md: how the code fits together and how to add a flag, option, provider, language or skill
• CODE_OF_CONDUCT.md: how we expect everyone to behave, and where to report problems
• SECURITY.md: please report security vulnerabilities privately, not in a public issue

MIT License