npm - @fernado03/zoo-flow - Versions diffs - 0.11.2 → 0.12.0 - Mend

@fernado03/zoo-flow 0.11.2 → 0.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (97) hide show

package/templates/full/.roo/skills/engineering/commit-and-document/SKILL.md CHANGED Viewed

@@ -1,163 +1,163 @@
----
-name: commit-and-document
-description: Stage selected files, write a Conventional Commit, optionally link a GitHub issue, and append a dated journal entry under docs/journal/. Use when the user wants to commit work and capture a local record of what changed.
----
-# Commit and Document
-Deterministic flow. Execute steps in order; do not deviate.
-## 1. Inspect git changes
-Run and read:
-- `git status --short`
-- `git diff --stat`
-- `git diff --cached --stat`
-Summarise: which files, what changed.
-If the working tree is clean, stop and report. Skip the rest.
-## 2. Propose a Conventional Commit
-One-line message:
-```
-<type>(<scope>): <short, action-focused summary>
-```
-- **type**: `feat`, `fix`, `refactor`, `docs`, `chore`, `test`, `style`, `perf`
-- **scope**: area touched. Omit parens if unclear.
-- **summary**: imperative, present tense, under 70 chars, starts with a verb.
-Show: proposed message, files to stage, files excluded (tests, docs, secrets). Ask: "Commit with this message? (yes / edit / cancel)". On `edit`, accept the user's revised message verbatim and re-run detection (step 2.5) on it before proceeding. On `cancel`, stop and report.
-## 2.5 Detect or ask for an issue reference
-Silent pre-checks first:
-1. `git remote -v` → bail if no `github.com` remote.
-2. `command -v gh` → bail if `gh` is not installed.
-Detection on the proposed message:
-- Closing keywords: `Closes/Close/Closed/Fixes/Fix/Fixed/Resolves/Resolve/Resolved #N` (case-insensitive)
-- Bare `#N` anywhere
-Branches:
-- **A — closing keyword present**: ask "After commit, comment on issue #N and close it? (yes / no)". `yes` → `{action: close, issue: N}`.
-- **B — bare `#N`**: ask "After commit, post a progress comment on issue #N? (yes / no / close)". Map to `comment` / `close` / none.
-- **C — no reference**: ask once "Is this commit related to a GitHub issue? (issue number / no / skip)". On a number, ask "Comment only or close after commit? (comment / close)". Anything non-numeric → none.
-Carry the result as `issue_action` (default `none`).
-## 3. Stage and commit
-Stage explicit files with `git add <file>...` (never `git add .`). Exclude:
-- anything under `test/`, `tests/`, `__tests__/`, `spec/`, `specs/`
-- files matching `*.test.*`, `*.spec.*`, `test_*`, `*_test.*`
-- anything that looks like secrets (`.env`, credentials, tokens)
-Flag exclusions to the user.
-Commit with the approved message. Capture the short hash via `git rev-parse --short HEAD`.
-## 3.5 Act on the issue reference
-If `issue_action` is `none`, skip.
-Otherwise build:
-```
-> *This was generated by AI during commit.*
-Linked from commit `<short-hash>`: <commit subject>
-```
-Run `gh issue comment <N> --body "<body>"`. If `action == close`, then run `gh issue close <N>` (never `--comment`; comment first).
-If either fails, report the error and continue. Do not abort. Do not close an issue you could not comment on.
-## 4. Ensure docs/ is gitignored
-Read `.gitignore`. If no line matches `docs/`, append:
-```
-# Local documentation — never committed
-docs/
-```
-Do not commit the gitignore change. If the user accidentally staged anything under `docs/`, unstage it (`git restore --staged docs/<path>`) and warn.
-## 5. Inspect existing docs/journal/
-List `docs/journal/` if present. If it uses a different date/file convention than the default below, follow its existing convention. Create the directory if missing.
-## 6. Write a dated entry
-Date via `date +%Y-%m-%d`. Create `docs/journal/<YYYY-MM-DD>/` if missing. Write `<HH-MM>-<short-slug>.md` (kebab-case slug, 3–6 words from the summary). Template:
-```md
-# <Commit summary>
-**Commit:** <full hash>
-**Short hash:** <short hash>
-**Date:** <YYYY-MM-DD HH:MM local time>
-## What changed
-<2–4 sentences. Plain English, not a file list.>
-## Why
-<1–3 sentences on motivation, pulled from conversation context.>
-## Notes for future me
-<Gotchas/follow-ups, one paragraph max. Skip if nothing worth saying.>
-```
-## 7. Surface stale docs (if any)
-Read `git diff --cached --stat`. If any staged path overlaps with a path
-referenced in `.zoo-flow/CONTEXT.md`, output exactly one line
-before "Confirm":
-  "Public surface may have drifted. Run /update-docs? (yes / skip)"
-On `yes` → suggest `/update-docs <area>`. On `skip` → continue.
-## 8. Confirm
-Report: commit hash + message, journal entry path, whether `.gitignore` was updated, and any issue actions taken. Close with: "All of `docs/` is gitignored, so this entry stays local."
-## Complete
-Call `attempt_completion` with:
-- commit hash (short)
-- journal entry path
-- status (complete / blocked with reason)
-- recommended next command
-Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
-## Context economy
-Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
-Prefer targeted `read_file` ranges or indentation/block reads once the relevant area is known.
-Read full files only when structure, ordering, or surrounding context is required for correctness.
-Do not re-read unchanged files; use prior findings unless the file changed.
-Use `git status --short`, `git diff --stat`, and targeted `git diff -- <file>` rather than dumping the full repo diff at once.
-## Safety
-- Never `git push`, `--amend`, `--force`, or `reset --hard`.
-- Flag suspected secrets; do not stage them.
-- If `git status` is clean, abort early.
+---
+name: commit-and-document
+description: Stage selected files, write a Conventional Commit, optionally link a GitHub issue, and append a dated journal entry under docs/journal/. Use when the user wants to commit work and capture a local record of what changed.
+---
+# Commit and Document
+Deterministic flow. Execute steps in order; do not deviate.
+## 1. Inspect git changes
+Run and read:
+- `git status --short`
+- `git diff --stat`
+- `git diff --cached --stat`
+Summarise: which files, what changed.
+If the working tree is clean, stop and report. Skip the rest.
+## 2. Propose a Conventional Commit
+One-line message:
+```
+<type>(<scope>): <short, action-focused summary>
+```
+- **type**: `feat`, `fix`, `refactor`, `docs`, `chore`, `test`, `style`, `perf`
+- **scope**: area touched. Omit parens if unclear.
+- **summary**: imperative, present tense, under 70 chars, starts with a verb.
+Show: proposed message, files to stage, files excluded (tests, docs, secrets). Ask: "Commit with this message? (yes / edit / cancel)". On `edit`, accept the user's revised message verbatim and re-run detection (step 2.5) on it before proceeding. On `cancel`, stop and report.
+## 2.5 Detect or ask for an issue reference
+Silent pre-checks first:
+1. `git remote -v` → bail if no `github.com` remote.
+2. `command -v gh` → bail if `gh` is not installed.
+Detection on the proposed message:
+- Closing keywords: `Closes/Close/Closed/Fixes/Fix/Fixed/Resolves/Resolve/Resolved #N` (case-insensitive)
+- Bare `#N` anywhere
+Branches:
+- **A — closing keyword present**: ask "After commit, comment on issue #N and close it? (yes / no)". `yes` → `{action: close, issue: N}`.
+- **B — bare `#N`**: ask "After commit, post a progress comment on issue #N? (yes / no / close)". Map to `comment` / `close` / none.
+- **C — no reference**: ask once "Is this commit related to a GitHub issue? (issue number / no / skip)". On a number, ask "Comment only or close after commit? (comment / close)". Anything non-numeric → none.
+Carry the result as `issue_action` (default `none`).
+## 3. Stage and commit
+Stage explicit files with `git add <file>...` (never `git add .`). Exclude:
+- anything under `test/`, `tests/`, `__tests__/`, `spec/`, `specs/`
+- files matching `*.test.*`, `*.spec.*`, `test_*`, `*_test.*`
+- anything that looks like secrets (`.env`, credentials, tokens)
+Flag exclusions to the user.
+Commit with the approved message. Capture the short hash via `git rev-parse --short HEAD`.
+## 3.5 Act on the issue reference
+If `issue_action` is `none`, skip.
+Otherwise build:
+```
+> *This was generated by AI during commit.*
+Linked from commit `<short-hash>`: <commit subject>
+```
+Run `gh issue comment <N> --body "<body>"`. If `action == close`, then run `gh issue close <N>` (never `--comment`; comment first).
+If either fails, report the error and continue. Do not abort. Do not close an issue you could not comment on.
+## 4. Ensure docs/ is gitignored
+Read `.gitignore`. If no line matches `docs/`, append:
+```
+# Local documentation — never committed
+docs/
+```
+Do not commit the gitignore change. If the user accidentally staged anything under `docs/`, unstage it (`git restore --staged docs/<path>`) and warn.
+## 5. Inspect existing docs/journal/
+List `docs/journal/` if present. If it uses a different date/file convention than the default below, follow its existing convention. Create the directory if missing.
+## 6. Write a dated entry
+Date via `date +%Y-%m-%d`. Create `docs/journal/<YYYY-MM-DD>/` if missing. Write `<HH-MM>-<short-slug>.md` (kebab-case slug, 3–6 words from the summary). Template:
+```md
+# <Commit summary>
+**Commit:** <full hash>
+**Short hash:** <short hash>
+**Date:** <YYYY-MM-DD HH:MM local time>
+## What changed
+<2–4 sentences. Plain English, not a file list.>
+## Why
+<1–3 sentences on motivation, pulled from conversation context.>
+## Notes for future me
+<Gotchas/follow-ups, one paragraph max. Skip if nothing worth saying.>
+```
+## 7. Surface stale docs (if any)
+Read `git diff --cached --stat`. If any staged path overlaps with a path
+referenced in `.zoo-flow/CONTEXT.md`, output exactly one line
+before "Confirm":
+  "Public surface may have drifted. Run /zoo-update-docs? (yes / skip)"
+On `yes` → suggest `/zoo-update-docs <area>`. On `skip` → continue.
+## 8. Confirm
+Report: commit hash + message, journal entry path, whether `.gitignore` was updated, and any issue actions taken. Close with: "All of `docs/` is gitignored, so this entry stays local."
+## Complete
+Call `attempt_completion` with:
+- commit hash (short)
+- journal entry path
+- status (complete / blocked with reason)
+- recommended next command
+Do NOT use `ask_followup_question` or write results as plain text without calling the tool.
+## Context economy
+Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
+Prefer targeted `read_file` ranges or indentation/block reads once the relevant area is known.
+Read full files only when structure, ordering, or surrounding context is required for correctness.
+Do not re-read unchanged files; use prior findings unless the file changed.
+Use `git status --short`, `git diff --stat`, and targeted `git diff -- <file>` rather than dumping the full repo diff at once.
+## Safety
+- Never `git push`, `--amend`, `--force`, or `reset --hard`.
+- Flag suspected secrets; do not stage them.
+- If `git status` is clean, abort early.

package/templates/full/.roo/skills/engineering/diagnose/SKILL.md CHANGED Viewed

@@ -37,7 +37,7 @@ Rules:
 ## 3. Hypotheses (with working memory)
-Initialize session: `.scratch/diagnoses/<YYYY-MM-DD>/diagnose-<slug>/`
+Initialize session: `.scratch/diagnoses/<YYYY-MM-DD>/zoo-diagnose-<slug>/`
 Write `<session-dir>/session.md` with symptom, repro steps, error signatures.
@@ -97,7 +97,7 @@ MUST finish:
 - [ ] `[DEBUG-...]` logs removed from source.
 - [ ] Throwaway harnesses deleted/moved.
 - [ ] Winning hypothesis stated in commit/PR.
-- [ ] Seam/locality blocker → recommend `/improve-codebase-architecture`.
+- [ ] Seam/locality blocker → recommend `/zoo-improve-codebase-architecture`.
 Tweaker MUST `switch_mode` back to `system-architect` for Phase 7.
@@ -133,4 +133,4 @@ Call `attempt_completion` with:
 - root cause summary
 - fix applied
 - status
-- recommended next command (typically `/verify` then `/review` then `/commit-and-document`)
+- recommended next command (typically `/zoo-verify` then `/zoo-review` then `/zoo-commit-and-document`)

package/templates/full/.roo/skills/engineering/grill-with-docs/SKILL.md CHANGED Viewed

@@ -16,7 +16,7 @@ description: Grilling session that challenges your plan against the existing dom
 ## Docs
-See `.roo/skills/engineering/grill-with-docs/CONTEXT-FORMAT.md` for layout and detection. Create docs lazily only when recording needed.
+See `.roo/skills/engineering/zoo-grill-with-docs/CONTEXT-FORMAT.md` for layout and detection. Create docs lazily only when recording needed.
 ## Context economy

package/templates/full/.roo/skills/engineering/improve-codebase-architecture/SKILL.md CHANGED Viewed

@@ -60,6 +60,6 @@ Call `attempt_completion` with:
 - candidates found (count and titles)
 - user selection (which candidate was chosen, if any)
 - status (complete / blocked with reason)
-- recommended next command (`/refactor` to implement the chosen candidate, or `/feature` if it requires PRD + issue slicing)
+- recommended next command (`/zoo-refactor` to implement the chosen candidate, or `/zoo-feature` if it requires PRD + issue slicing)
 Do NOT use `ask_followup_question` or write results as plain text without calling the tool.

package/templates/full/.roo/skills/engineering/prototype/SKILL.md CHANGED Viewed

@@ -1,47 +1,47 @@
----
-name: prototype
-description: Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
----
-# Prototype
-RULE: Prototype answers one question. Throw away or absorb after answer.
-## Branch
-- Logic/state/data-model → `LOGIC.md`.
-- Visual/layout/UI → `UI.md`.
-- Ambiguous → ask.
-- User AFK → infer + state assumption.
-## Context economy
-Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
-Prefer targeted `read_file` ranges or indentation/block reads once the relevant area is known.
-Read full files only when structure, ordering, or surrounding context is required for correctness.
-Do not re-read unchanged files; use prior findings unless the file changed.
-## Rules
-1. Mark throwaway clearly.
-2. Place under `.scratch/prototypes/<slug>/` (logic/state/data-model) or near the real module/page (UI). UI prototypes need the real route, data fetching, and auth, so they stay adjacent to the page they mock up; logic prototypes have no such constraint, so they go in `.scratch/` with the other throwaway work.
-3. Follow existing routing/tooling.
-4. Provide one run command.
-5. Default no persistence; state in memory.
-6. Persistence target → scratch DB/file named `PROTOTYPE — wipe me` in the prototype folder.
-7. No polish: no tests, minimal errors, no abstractions.
-8. Surface full relevant state after each action/variant switch.
-9. Done → capture answer in commit (only after explicit user approval)/ADR/issue/`NOTES.md`; delete or fold into real code.
-## Complete
-Call `attempt_completion` with:
-- question answered
-- prototype location (`.scratch/prototypes/<slug>/` or real module path)
-- outcome (absorbed / discarded / needs decision)
-- recommended next command
-Do NOT end the task with `ask_followup_question` or write results as plain text without calling the tool.
+---
+name: prototype
+description: Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
+---
+# Prototype
+RULE: Prototype answers one question. Throw away or absorb after answer.
+## Branch
+- Logic/state/data-model → `LOGIC.md`.
+- Visual/layout/UI → `UI.md`.
+- Ambiguous → ask.
+- User AFK → infer + state assumption.
+## Context economy
+Before broad reads, locate relevant files/symbols with `list_files`, `search_files`, or `codebase_search`.
+Prefer targeted `read_file` ranges or indentation/block reads once the relevant area is known.
+Read full files only when structure, ordering, or surrounding context is required for correctness.
+Do not re-read unchanged files; use prior findings unless the file changed.
+## Rules
+1. Mark throwaway clearly.
+2. Place under `.scratch/prototypes/<slug>/` (logic/state/data-model) or near the real module/page (UI). UI prototypes need the real route, data fetching, and auth, so they stay adjacent to the page they mock up; logic prototypes have no such constraint, so they go in `.scratch/` with the other throwaway work.
+3. Follow existing routing/tooling.
+4. Provide one run command.
+5. Default no persistence; state in memory.
+6. Persistence target → scratch DB/file named `PROTOTYPE — wipe me` in the prototype folder.
+7. No polish: no tests, minimal errors, no abstractions.
+8. Surface full relevant state after each action/variant switch.
+9. Done → capture answer in commit (only after explicit user approval)/ADR/issue/`NOTES.md`; delete or fold into real code.
+## Complete
+Call `attempt_completion` with:
+- question answered
+- prototype location (`.scratch/prototypes/<slug>/` or real module path)
+- outcome (absorbed / discarded / needs decision)
+- recommended next command
+Do NOT end the task with `ask_followup_question` or write results as plain text without calling the tool.

package/templates/full/.roo/skills/engineering/review/SKILL.md CHANGED Viewed

@@ -41,7 +41,7 @@ Read relevant specs, issues, PRDs, standards, docs, ADRs, security notes, or pro
 ## 3. Review axes (multi-pass with working memory)
-Initialize session: `.scratch/reviews/<YYYY-MM-DD>/review-<slug>/`
+Initialize session: `.scratch/reviews/<YYYY-MM-DD>/zoo-review-<slug>/`
 Write `<session-dir>/session.md` with review target, base ref, scope.
@@ -136,11 +136,11 @@ Do NOT use `ask_followup_question` or write results as plain text without callin
 If fixes are needed, recommend one next command only:
-- small fix -> `/tweak`
-- behavior fix -> `/tdd`
-- unknown cause -> `/fix`
-- design issue -> `/refactor`
-- ready for evidence -> `/verify`
-- ready to commit -> `/commit-and-document`
+- small fix -> `/zoo-tweak`
+- behavior fix -> `/zoo-tdd`
+- unknown cause -> `/zoo-fix`
+- design issue -> `/zoo-refactor`
+- ready for evidence -> `/zoo-verify`
+- ready to commit -> `/zoo-commit-and-document`
 Do not auto-launch any follow-up command.