quiver-cli 1.3.1 → 2.0.0

package/package.json

@@ -1,15 +1,14 @@
 {
   "name": "quiver-cli",
-  "version": "1.3.1",
-  "description": "Compose selected skills, commands, plugins and MCP servers from a central catalog into any repo as native configs for opencode, Claude Code and Codex - with lockfile-based drift awareness.",
+  "version": "2.0.0",
+  "description": "Install agent skills from direct GitHub sources, plus custom skills, commands, plugins and MCP servers from catalogs, as native configs for opencode, Claude Code and Codex with per-entry source pins and drift checks.",
   "type": "module",
   "bin": {
     "quiver-cli": "bin/quiver-cli.mjs"
   },
   "files": [
     "bin",
-    "dist",
-    "template"
+    "dist"
   ],
   "engines": {
     "node": ">=20.12.0"
@@ -26,16 +25,16 @@
   ],
   "packageManager": "pnpm@8.15.6",
   "dependencies": {
-    "@clack/prompts": "^1.5.1",
+    "@clack/prompts": "^1.7.0",
     "@iarna/toml": "^2.2.5",
-    "@modelcontextprotocol/sdk": "^1.12.0",
-    "tar": "^7.5.16"
+    "@modelcontextprotocol/sdk": "^1.30.0",
+    "tar": "^7.5.22"
   },
   "devDependencies": {
-    "@types/node": "^22.10.2",
-    "tsup": "^8.3.5",
-    "typescript": "^5.7.2",
-    "vitest": "^2.1.8"
+    "@types/node": "^22.20.1",
+    "tsup": "^8.5.1",
+    "typescript": "^7.0.2",
+    "vitest": "^5.0.0"
   },
   "publishConfig": {
     "access": "public"

package/template/.agents/AGENTS.md

@@ -1,26 +0,0 @@
-# AGENTS.md
-
-Guide for coding agents working in this repository.
-
-## Agent Setup
-
-Agent configuration (skills, commands, plugins, MCP servers) lives in `.agents/` — the
-single source of truth, managed by [quiver-cli](https://github.com/nbialk/quiver-cli):
-
-- `.agents/skills/` — agent skills (SKILL.md directories).
-- `.agents/commands/` — slash commands.
-- `.agents/plugins/` — provider-specific local plugins.
-- `.agents/config.json` — MCP servers, plugins and provider overlays.
-- `quiver.lock` — locked state with content digests.
-
-Provider files (`.claude/`, `.opencode/`, `.codex/`, `.mcp.json`,
-`opencode.json`) are **generated** from `.agents/` and gitignored. Do not edit
-them directly.
-
-## Workflow
-
-- `quiver-cli sync` — regenerate provider configs from `.agents/`.
-- `quiver-cli check` — verify lockfile, shims and MCP tool snapshots.
-- `quiver-cli add/remove <id>` — change what is installed.
-- Commit `.agents/` and `quiver.lock`; never commit generated provider files
-  or `.env.local`.

package/template/.agents/commands/cp.md

@@ -1,108 +0,0 @@
----
-description: Commit and push all current changes using Conventional Commits
-subtask: true
----
-
-You are a git commit assistant. Your job is to stage changes, create well-formed Conventional Commit messages, and push to the remote.
-
-## Context
-
-Status:
-!`git status`
-
-Summary:
-!`git diff --stat`
-
-## Steps
-
-### 1. Inspect Changes
-
-Review the status and summary above to understand the current state.
-
-If there are no changes (nothing to commit), respond with "Nothing to commit." and stop.
-
-### 2. Analyze Changes
-
-Review the diff to understand what changed:
-
-```bash
-git diff HEAD
-```
-
-### 3. Split Commits if Necessary
-
-If changes are **unrelated** (e.g., a bug fix and a new feature), split them into separate commits. Each commit must represent **one logical change**.
-
-To split: stage the relevant files selectively with `git add <file>`, commit, then repeat for the next logical change.
-
-### 4. Select Commit Type
-
-Choose the most accurate type:
-
-| Type       | When to use                         |
-| ---------- | ----------------------------------- |
-| `feat`     | New user-facing behavior            |
-| `fix`      | Bug fix                             |
-| `refactor` | Internal change, no behavior change |
-| `docs`     | Documentation only                  |
-| `style`    | Formatting only                     |
-| `perf`     | Performance improvement             |
-| `test`     | Tests only                          |
-| `chore`    | Tooling, config, deps               |
-| `ci`       | CI/CD only                          |
-
-### 5. Compose Commit Message
-
-Format: `<type>(<scope>): <subject>`
-
-**Scope rules:**
-
-- Include scope if change affects a specific module (e.g., `chat`, `jira`, `auth`, `admin`)
-- Omit scope only if change is truly global
-- Lowercase, single word
-
-**Subject rules:**
-
-- Imperative mood ("add", "fix", "remove" — not "added", "fixed", "removed")
-- Max 72 characters
-- No period at end
-
-**Body rules:**
-
-- REQUIRED if >3 files changed OR a new concept is introduced
-- Otherwise omit
-- Separate from subject with a blank line
-
-**Forbidden subjects:** `update`, `wip`, `changes`, `fix stuff`, `misc`
-
-### 6. Execute
-
-Stage only the files belonging to the current logical change — never use `git add -A`:
-
-```bash
-git add <file1> <file2> ...
-git commit -m "<message>"
-```
-
-If splitting commits, repeat the add/commit cycle per logical change. Push once at the end:
-
-- If the current branch has no upstream, set it: `git push -u origin HEAD`
-- Otherwise: `git push`
-
-### 7. Report
-
-After pushing, show a summary:
-
-```
-Pushed to <branch>:
-- <commit hash> <commit message>
-- <commit hash> <commit message> (if multiple)
-```
-
-## Rules
-
-- Stage selectively per logical change; NEVER use `git add -A`.
-- NEVER amend existing commits.
-- NEVER force push.
-- NEVER create empty commits.
-- If push fails due to remote being ahead, run `git pull --rebase` first, then push again.