pakhale 0.2.0 → 0.4.0

package/README.md

@@ -38,11 +38,25 @@ Agents package things differently, so each capability says how it reaches each a
 Leaving an agent undeclared is an error rather than a silent skip, so adding a new agent tells
 me about every gap at once.
 
+## Just the skills
+
+The skills in [`skills/`](skills/) are plain `SKILL.md` files, so they need neither this CLI
+nor my settings. Any agent that reads skills can install them straight from this repo:
+
+```bash
+npx skills add pratikpakhale/pakhale -g                    # all of them
+npx skills add pratikpakhale/pakhale -g -s deslop stackup  # or pick
+```
+
+`npx pakhale setup agents` stays the full path — the same skills plus plugins, MCP servers,
+instructions and settings.
+
 ## Options
 
 - `plan` or `-n, --dry-run` — show every change, write nothing
 - `-a, --agent <id>` — set up one agent (repeatable)
 - `--all` — every configured agent, no prompt
+- `--force` — resolve every conflict in the config's favour, no prompts
 - `--home <dir>` — apply against a different home directory
 - `-h, --help` — full usage
 
@@ -53,6 +67,10 @@ Piped or scripted, it applies to every configured agent without asking.
 
 - **Re-running changes nothing.** Every artifact is checked before it is written, installers
   included.
+- **Nothing of yours is overwritten silently.** Setup remembers what it last wrote; anything
+  else it finds — an existing `CLAUDE.md`, a setting changed by hand — is a conflict, and it
+  asks: keep yours, use the config's (backed up first), or see the diff, with one answer for
+  all remaining if you prefer. Piped runs keep yours; `--force` takes the config's.
 - **Settings you added yourself survive.** Keys `config.ts` does not name are preserved.
 - **A config file it cannot parse is left alone** rather than flattened.
 - **Agents you do not have installed are skipped,** never created.