quiver-cli 0.1.0

package/package.json

@@ -0,0 +1,55 @@
+{
+  "name": "quiver-cli",
+  "version": "0.1.0",
+  "description": "Compose a selected subset of skills, commands & MCP servers from a central catalog into any repo as native configs for opencode, Claude Code and Codex - with lockfile-based drift awareness.",
+  "type": "module",
+  "bin": {
+    "quiver-cli": "bin/quiver-cli.mjs"
+  },
+  "files": [
+    "bin",
+    "dist",
+    "template"
+  ],
+  "engines": {
+    "node": ">=20.12.0"
+  },
+  "keywords": [
+    "agents",
+    "agent-skills",
+    "mcp",
+    "claude-code",
+    "opencode",
+    "codex",
+    "cli",
+    "lockfile"
+  ],
+  "packageManager": "pnpm@8.15.6",
+  "dependencies": {
+    "@clack/prompts": "^1.5.1",
+    "@iarna/toml": "^2.2.5",
+    "@modelcontextprotocol/sdk": "^1.12.0",
+    "tar": "^7.5.16"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.2",
+    "tsup": "^8.3.5",
+    "typescript": "^5.7.2",
+    "vitest": "^2.1.8"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/nbialk/quiver-cli.git"
+  },
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch",
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run",
+    "test:watch": "vitest"
+  }
+}

package/template/.agents/AGENTS.md

@@ -0,0 +1,25 @@
+# AGENTS.md
+
+Guide for coding agents working in this repository.
+
+## Agent Setup
+
+Agent configuration (skills, commands, 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/config.json` — MCP servers and shared settings.
+- `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 status` — verify lockfile and shims are in sync.
+- `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

@@ -0,0 +1,116 @@
+---
+description: Commit and push all current changes using Conventional Commits
+---
+
+You are a git commit assistant. Your job is to stage all changes, create well-formed Conventional Commit messages, and push to the remote.
+
+## Steps
+
+### 1. Inspect Changes
+
+Run these commands to understand the current state:
+
+```bash
+git status
+git diff --stat
+```
+
+If there are no changes (nothing to commit), respond with "Nothing to commit." and stop.
+
+### 2. Prisma Migration Check
+
+If `prisma/schema.prisma` appears in the changed files, verify that migration files also exist in the changeset:
+
+```bash
+SCHEMA_CHANGED=$(git diff --name-only HEAD -- prisma/schema.prisma)
+MIGRATION_CHANGED=$(git diff --name-only HEAD -- prisma/migrations/)
+```
+
+If `SCHEMA_CHANGED` is non-empty but `MIGRATION_CHANGED` is empty, a migration is missing. Create one:
+
+1. Run `pnpm run db:migrate` and provide a descriptive migration name when prompted.
+2. After the migration is created, verify it exists in `prisma/migrations/`.
+3. The new migration files will be included in the commit automatically (via `git add -A`).
+
+If both are non-empty or schema is unchanged, proceed normally.
+
+### 3. Analyze Changes
+
+Review the diff to understand what changed:
+
+```bash
+git diff HEAD
+```
+
+### 4. 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 files selectively with `git add <file>`, commit, then repeat.
+
+### 5. 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                          |
+
+### 6. 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`
+
+### 7. Execute
+
+```bash
+git add -A
+git commit -m "<message>"
+git push -u origin HEAD
+```
+
+If splitting commits, repeat the add/commit cycle per logical change, then push once at the end.
+
+### 8. Report
+
+After pushing, show a summary:
+
+```
+Pushed to <branch>:
+- <commit hash> <commit message>
+- <commit hash> <commit message> (if multiple)
+```
+
+## Rules
+
+- 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.