{"owner":"steipete","repo":"summarize","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Summarize Guardrails\n\n- Hard rule: single source of truth = `~/Projects/summarize`; never commit in `vendor/summarize` (treat it as a read-only checkout).\n- Note: multiple agents often work in this folder. If you see files/changes you do not recognize, ignore them and list them at the end.\n\n## Workspace layout (note)\n\n- Monorepo (pnpm workspace).\n- Packages:\n  - `@steipete/summarize` = CLI + UX (TTY/progress/streaming). Depends on core.\n  - `@steipete/summarize-core` (`packages/core`) = library surface for programmatic use (Sweetistics etc). No CLI entrypoints.\n- Versioning: lockstep versions; publish order: core first, then CLI (`scripts/release.sh` / `RELEASING.md`).\n- Homebrew/core formula is not owned here; BrewTestBot autobumps releases about every 3h. Do not block or manually manage it; ship and continue.\n- Chrome Web Store: every release must upload the matching `dist-chrome/summarize-chrome-extension-v<version>.zip` to item `cejgnmmhbbpdmjnfppjdfkocebngehfg`, submit it for review with automatic publishing, and verify the exact pending/published version. Skip only when every shipped change is daemon-side and the packaged extension/companion contract is unchanged.\n- Dev:\n  - Build: `pnpm -s build` (builds core first)\n  - Gate: `pnpm -s check`\n  - Import from apps: prefer `@steipete/summarize-core` to avoid pulling CLI-only deps.\n- Dependencies: stable releases need a 7-day stabilization delay before adoption; prereleases remain excluded unless already adopted.\n- Daemon: restart with `pnpm -s summarize daemon restart`; verify via `pnpm -s summarize daemon status`.\n- Rebuild (extension + daemon): run **both** in order:\n  1. `pnpm -C apps/chrome-extension build`\n  2. `pnpm summarize daemon restart`\n- Extension tests:\n  - `pnpm -C apps/chrome-extension test:chrome` = supported automated path.\n  - Firefox Playwright extension tests are not reliable (`moz-extension://` limitation); default `test:firefox` skips.\n  - Use `pnpm -C apps/chrome-extension test:firefox:force` only for explicit diagnostics.\n- Commits: use `committer \"type: message\" <files...>` (Conventional Commits).\n"},"files":{"AGENTS.md":"# Summarize Guardrails\n\n- Hard rule: single source of truth = `~/Projects/summarize`; never commit in `vendor/summarize` (treat it as a read-only checkout).\n- Note: multiple agents often work in this folder. If you see files/changes you do not recognize, ignore them and list them at the end.\n\n## Workspace layout (note)\n\n- Monorepo (pnpm workspace).\n- Packages:\n  - `@steipete/summarize` = CLI + UX (TTY/progress/streaming). Depends on core.\n  - `@steipete/summarize-core` (`packages/core`) = library surface for programmatic use (Sweetistics etc). No CLI entrypoints.\n- Versioning: lockstep versions; publish order: core first, then CLI (`scripts/release.sh` / `RELEASING.md`).\n- Homebrew/core formula is not owned here; BrewTestBot autobumps releases about every 3h. Do not block or manually manage it; ship and continue.\n- Chrome Web Store: every release must upload the matching `dist-chrome/summarize-chrome-extension-v<version>.zip` to item `cejgnmmhbbpdmjnfppjdfkocebngehfg`, submit it for review with automatic publishing, and verify the exact pending/published version. Skip only when every shipped change is daemon-side and the packaged extension/companion contract is unchanged.\n- Dev:\n  - Build: `pnpm -s build` (builds core first)\n  - Gate: `pnpm -s check`\n  - Import from apps: prefer `@steipete/summarize-core` to avoid pulling CLI-only deps.\n- Dependencies: stable releases need a 7-day stabilization delay before adoption; prereleases remain excluded unless already adopted.\n- Daemon: restart with `pnpm -s summarize daemon restart`; verify via `pnpm -s summarize daemon status`.\n- Rebuild (extension + daemon): run **both** in order:\n  1. `pnpm -C apps/chrome-extension build`\n  2. `pnpm summarize daemon restart`\n- Extension tests:\n  - `pnpm -C apps/chrome-extension test:chrome` = supported automated path.\n  - Firefox Playwright extension tests are not reliable (`moz-extension://` limitation); default `test:firefox` skips.\n  - Use `pnpm -C apps/chrome-extension test:firefox:force` only for explicit diagnostics.\n- Commits: use `committer \"type: message\" <files...>` (Conventional Commits).\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Summarize Guardrails\n\n- Hard rule: single source of truth = `~/Projects/summarize`; never commit in `vendor/summarize` (treat it as a read-only checkout).\n- Note: multiple agents often work in this folder. If you see files/changes you do not recognize, ignore them and list them at the end.\n\n## Workspace layout (note)\n\n- Monorepo (pnpm workspace).\n- Packages:\n  - `@steipete/summarize` = CLI + UX (TTY/progress/streaming). Depends on core.\n  - `@steipete/summarize-core` (`packages/core`) = library surface for programmatic use (Sweetistics etc). No CLI entrypoints.\n- Versioning: lockstep versions; publish order: core first, then CLI (`scripts/release.sh` / `RELEASING.md`).\n- Homebrew/core formula is not owned here; BrewTestBot autobumps releases about every 3h. Do not block or manually manage it; ship and continue.\n- Chrome Web Store: every release must upload the matching `dist-chrome/summarize-chrome-extension-v<version>.zip` to item `cejgnmmhbbpdmjnfppjdfkocebngehfg`, submit it for review with automatic publishing, and verify the exact pending/published version. Skip only when every shipped change is daemon-side and the packaged extension/companion contract is unchanged.\n- Dev:\n  - Build: `pnpm -s build` (builds core first)\n  - Gate: `pnpm -s check`\n  - Import from apps: prefer `@steipete/summarize-core` to avoid pulling CLI-only deps.\n- Dependencies: stable releases need a 7-day stabilization delay before adoption; prereleases remain excluded unless already adopted.\n- Daemon: restart with `pnpm -s summarize daemon restart`; verify via `pnpm -s summarize daemon status`.\n- Rebuild (extension + daemon): run **both** in order:\n  1. `pnpm -C apps/chrome-extension build`\n  2. `pnpm summarize daemon restart`\n- Extension tests:\n  - `pnpm -C apps/chrome-extension test:chrome` = supported automated path.\n  - Firefox Playwright extension tests are not reliable (`moz-extension://` limitation); default `test:firefox` skips.\n  - Use `pnpm -C apps/chrome-extension test:firefox:force` only for explicit diagnostics.\n- Commits: use `committer \"type: message\" <files...>` (Conventional Commits).\n","category":"root","tokens":529}]}