projectops 4.48.1 → 4.49.0

package/README.md

@@ -2,6 +2,8 @@
 
 <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.**
+
 [한국어](docs/i18n/README.ko.md) | **English** | [简体中文](docs/i18n/README.zh-CN.md) | [日本語](docs/i18n/README.ja.md)
 
 [![npm](https://img.shields.io/npm/v/projectops?label=npm)](https://www.npmjs.com/package/projectops) [![Release](https://img.shields.io/github/v/release/Cassiiopeia/projectops?label=release)](https://github.com/Cassiiopeia/projectops/releases) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![Docs](https://img.shields.io/badge/docs-site-4f46e5)](https://cassiiopeia.github.io/projectops/)
@@ -9,7 +11,7 @@
 **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](https://github.com/Cassiiopeia/projectops/releases)).
 
 <!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->
-## Latest version : v4.48.0 (2026-10-12)
+## Latest version : v4.48.1 (2026-10-12)
 
 [View full version history](CHANGELOG.md)
 
@@ -39,7 +41,7 @@
 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 write issues, commit messages, and implementation reports for you.
+**② 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 |
 |----------|---------------------|
@@ -47,9 +49,9 @@ This project automates your development workflow on two axes.
 | 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 |
+| 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 |
+| Re-type prompts for every code review or analysis | 14 skills give consistent results without re-typing |
 
 ---
 
@@ -63,7 +65,7 @@ If you only need one piece of this, a smaller tool may suit you better.
 | 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, Node, Python ...) | No | No | No |
-| Issue and PR helpers, Agent Skills | Yes | 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 50 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.
@@ -84,19 +86,54 @@ Below is a **real run, recorded** after installing projectops in a sample repo i
 
 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
 
 ![Change summary comment after opening a PR](https://raw.githubusercontent.com/Cassiiopeia/projectops/main/docs/images/feature-pr-summary.gif)
 
 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
 
 ![Release PR merging automatically and a tag appearing](https://raw.githubusercontent.com/Cassiiopeia/projectops/main/docs/images/feature-release.gif)
 
 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.
+
+```json
+{
+  "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](docs/en/skills.md).
+
+### Example: /pro-oss-consult on this repo
+
+We ran `/pro-oss-consult` on this repo, then fixed what it found (measured 2026-10-13).
+
+| Check | Before | After |
+|---|---|---|
+| Skill count stated in README and manifests | inconsistent (15 vs 20 stated, actual 15) | consistent: 14 core + 1 in the optional extras plugin |
+| Longest skill description | 1,183 chars; 6 over 1,000 | 237 chars; 0 over 300 |
+| Skills with no tests (all 15 skills) | 6 | 0 (56 contract test cases cover all 15 skills, 14 core + 1 extras) |
+| Commit format | hardcoded in `pro-commit` | configurable via preferences and `version.yml` |
+
+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
@@ -104,18 +141,18 @@ Open a PR from the development branch to `main` and it writes the release notes,
 | Part | What it does | Docs |
 |---|---|---|
 | **GitHub Actions** | One push to main handles versioning, changelogs, and CI/CD deployment | [Versioning](https://cassiiopeia.github.io/projectops/VERSION-CONTROL) (Korean) |
-| **Agent Skills** (20) | `/pro-github`, `/pro-commit`, `/pro-report` and more let an AI agent write issues, commit messages, and implementation reports | [Skills guide](https://cassiiopeia.github.io/projectops/SKILLS) (Korean) |
+| **Agent Skills** (14) | `/pro-github`, `/pro-commit`, `/pro-report` and more let an AI agent drive each step: issues, commits in your style, reports, release PRs | [Skills guide](https://cassiiopeia.github.io/projectops/SKILLS) (Korean) |
 | **npx CLI** | Installs and updates workflows in an existing project, and diagnoses its state | [CLI reference](https://cassiiopeia.github.io/projectops/en/cli) |
 
 <details>
-<summary>See all 20 Agent Skills</summary>
+<summary>See all 14 Agent Skills</summary>
 
 ### 🔄 Development cycle automation
 
 | Skill | Purpose |
 |------|------|
 | `/pro-init-worktree` | Create a Git worktree and copy sensitive files automatically |
-| `/pro-commit` | Complete a commit message from the issue context (follows superpowers) |
+| `/pro-commit` | Complete a commit message from the issue context, in your own format (preset or template) |
 | `/pro-report` | Analyze the git diff → generate an implementation report and post it as a GitHub comment |
 | `/pro-changelog-deploy` | Push develop → open the main release PR + write release notes + automerge |
 | `/pro-github` | GitHub in general: create issues (one-line description → template + file), view/edit/comment/label/assign, create/merge/view PRs, explore repos, manage Actions and Secrets |
@@ -143,10 +180,11 @@ Open a PR from the development branch to `main` and it writes the release notes,
 |------|------|
 | `/pro-testcase` | Analyze an issue → generate a QA checklist |
 | `/pro-agent-test` | QA that actually runs apps, web, and servers to find bugs, reporting reproduction steps, evidence, and severity (it does not fix code) |
-| `/pro-synology-expose` | Guide to exposing a Synology NAS service on an external domain |
 | `/pro-ssh` | Connect to a remote server over SSH and run commands (AWS EC2, Synology NAS, Linux, and more) |
 | `/pro-skill-creator` | Create, review, and improve a Skill (CREATE / REVIEW / IMPROVE modes) |
 
+**Extras** (optional plugin): `/pro-synology-expose` — `claude plugin install projectops-extras@projectops-marketplace --scope user`
+
 </details>
 
 <details>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectops",
-  "version": "4.48.1",
+  "version": "4.49.0",
   "description": "ProjectOps: installer CLI for a fully automated GitHub project management template (versioning, CI/CD, release notes, agent skills)",
   "keywords": [
     "devops",

package/src/core/exclusions.js

@@ -29,6 +29,7 @@ export const PLUGIN_ITEMS_TO_REMOVE = [
   "scripts",
   "package.json",
   "harness",
+  "plugins",
   "bin",
   "src",
   "site",