@uge/payo 2.1.2 → 2.2.0

package/README.md

@@ -161,7 +161,8 @@ When detection finds a manifest, you get two quick choices:
     **skips anything it can't find**: no skill is created for it and it isn't
     mentioned. The only things applied without detection are a few safe assistant
     policies (no AI attribution in commits, task-scoped atomic commits, confirm
-    before push, verify before push, work from `.env.example`, and DRY/modular
+    before push, verify before push, gitleaks secret scan before push, confirm
+    before destructive SQL / migrations, work from `.env.example`, and DRY/modular
     coding standards) — all shown up front and editable on the review screen. You
     land straight on that review screen and confirm once.
   - **Just the high-level stack** fills in the stack facts only and interviews you
@@ -232,6 +233,28 @@ if you opt in, it asks when to run — before every commit or before pushing —
 agent uses it at that point to check your pending change against the relevant project
 skills and flag anything that conflicts.
 
+### Guardrails enforced by hooks, not just prose
+
+Skills are guidance the assistant _should_ follow — but an agent can skip prose. So
+when you enable a guardrail, Payo also writes the hook that makes it fire regardless:
+
+- **A git hook (mechanical, hard block).** When you turn on the gitleaks scan or the
+  verify-before-commit/push step, Payo writes a **`lefthook.yml`** (or, if your repo
+  already uses **husky**, **pre-commit**, or native `.git/hooks`, merges into _that_
+  runner instead — never clobbering your setup). It runs `gitleaks` and your test
+  command at the stage you chose and **blocks the commit/push on failure** — for every
+  tool, and for a human typing `git`. Payo writes the config; you wire it up once with
+  `lefthook install` (Payo tells you the command; it installs nothing itself).
+- **A native tool hook (soft confirm).** For **Claude, Cursor, and Copilot**, Payo
+  writes a `PreToolUse` hook that pops a **confirm prompt** right when the agent runs
+  `git commit` / `git push` (to run change-audit or confirm the push) or a destructive
+  query (DB-safety). It stores no state and runs no model — it just makes the prompt
+  appear so the guardrail isn't silently skipped. Tools without a soft-confirm hook
+  (Codex, Antigravity, Windsurf) are covered by the git hook above.
+
+Both are **idempotent** — re-running Payo never duplicates a hook — and are written
+only for the guardrails you actually enabled.
+
 The question Payo asks — _"Which agent CLI should Payo use to generate content?"_ —
 picks only **which installed CLI authors the content**. The output above works with
 every skills-compatible tool regardless of that choice.
@@ -246,23 +269,27 @@ every skills-compatible tool regardless of that choice.
 ## What it asks about
 
 Payo understands **30 frameworks, 29 ORMs, and 17 databases** across
-**TypeScript/JavaScript, Python, Go, Rust, PHP, C#, Java, and Ruby** — and tailors its follow-up
-questions to whatever you pick. Dimensions covered:
+**TypeScript/JavaScript, Python, Go, Rust, PHP, C#, Java, and Ruby** — backed by a
+bank of **200+ stack-tailored questions** it draws from, asking only the handful
+your stack needs. Dimensions covered:
 
 - **Project** — type (frontend / backend / full-stack / CLI / script) and a short description
 - **Language & framework** — plus framework-specific conventions
 - **API** — REST, GraphQL, gRPC, tRPC
 - **Frontend** — styling and state management, with provider-specific
   conventions for Tailwind, shadcn/ui, and CSS Modules
-- **Data** — database and ORM/data-layer, with naming & migration conventions
+- **Data** — database and ORM/data-layer, with naming & migration conventions,
+  plus a guardrail requiring confirmation before destructive SQL or migrations
 - **Auth** — approach, session strategy, RBAC, plus provider-specific
   conventions for Clerk, Auth.js, Better Auth, and Supabase Auth
 - **Validation & logging** — stack-appropriate libraries
 - **Testing** — unit / integration / component / E2E and runners
 - **Tooling** — package manager, runtime, formatter, linter
 - **TypeScript** — `tsconfig` strictness, target, module resolution, path aliases
-- **Conventions** — folder structure, coding standards, docs, git workflow, and
-  branch-naming / commit-message style (inferred from local git history)
+- **Conventions** — folder structure, coding standards, docs, git workflow,
+  branch-naming / commit-message style (inferred from local git history), and an
+  option to add a gitleaks secret-scan convention (scan for leaked secrets before
+  every push)
 - **Change audit** _(optional)_ — opt into a skill that checks your pending
   change against the project skills before commit or push