@zebeqo/vendy 0.1.1 → 0.1.2

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 (2) hide show
  1. package/dist/main.mjs +3 -3
  2. package/package.json +1 -1
package/dist/main.mjs CHANGED
@@ -45600,8 +45600,8 @@ const skills$1 = {
45600
45600
  content: "---\nname: research\ndescription: Before building a feature, find what it should be built on or modeled after — what the map already covers, then three to five current, credible open-source candidates laid out with the data to choose between them. Ends when the user picks one and the vendor workflow takes over.\n---\n\n# research a feature\n\nDo not write the feature yet. Find what it should stand on, so nothing is reinvented and nothing is guessed.\n\n## 1. Pin down the feature\n\nOne sentence: what it does for the user of this project, and what it touches. If the request leaves that open, ask before searching — candidates are only comparable against a stated need.\n\n## 2. Look in the map first\n\n```bash\nvendy catalog\n```\n\nA repo already here may cover it. A framework the project is built on often ships the feature itself — a local database on an Effect project means Effect's own SQL modules before any new library — and a project already imitated may already solve the same problem. Read the relevant snapshot far enough to say yes or no.\n\nIf the map covers it, say so, name the evidence (`.vendy/<name>/<path>`), and offer to go straight to building. Research continues only if the user wants alternatives.\n\n## 3. Find candidates\n\nTwo kinds, and say which each one is:\n\n- **Library** — the project would depend on it.\n- **Reference** — a project that already ships this feature well, to imitate its implementation and its UX.\n\nSources: `gh search repos <terms> --sort stars --limit 20`, web search for recent comparisons and announcements, and the dependencies and choices of the high-quality projects already vendored. Prefer what is actively developed: the user favors newer tools with cleaner designs over incumbents, so a young project with momentum is a real candidate, not a risk to filter out.\n\n## 4. Gather the facts\n\nFor each candidate:\n\n```bash\ngh repo view <owner>/<repo> --json stargazerCount,pushedAt,licenseInfo,latestRelease,description\ngh release list --repo <owner>/<repo> --limit 5\ngh api 'repos/<owner>/<repo>/git/trees/HEAD?recursive=1' \\\n --jq '[.tree[] | select(.type == \"blob\")] as $b | {truncated, files: ($b | length), bytes: ($b | map(.size) | add)}'\n```\n\nThe last one sizes the snapshot: the files at the default branch's tip, which is what vendoring puts on disk. Not `diskUsage` from `gh repo view`, which counts the whole history and overstates a large repository several times over. `truncated: true` means the tree is too large for one response; report it as very large.\n\nRead its README and enough of its docs or source to judge fit with this project's stack — whether it is native to the framework the project already uses, its runtime, its module format.\n\n## 5. Present the options\n\nThree to five candidates in one table, then a recommendation:\n\n| Candidate | Kind | Stars | Last release | Last push | License | Snapshot | Fit with this project | Why it stands out |\n| --------- | ---- | ----: | ------------ | --------- | ------- | -------: | --------------------- | ----------------- |\n\nWrite the snapshot as files and megabytes (`2,628 files, 41 MB`). No hard thresholds: show the numbers and let the user weigh them. A large snapshot is not a reason to drop a candidate; it is a reason to vendor only the paths the use needs (vendor workflow), so say which ones when it is. The recommendation names one candidate and the reason, citing what you read.\n\n## 6. Hand off\n\nWhen the user picks, load `vendy skills get vendor` and vendor it with the feature as the purpose — unless it fails that workflow's \"Is it worth a repo?\", in which case it becomes a dependency without a repo. A pick of \"none\" ends here with nothing vendored.\n"
45601
45601
  },
45602
45602
  "review": {
45603
- description: "Review the current branch's changes against the map — the health check narrowed to the files the branch touched: does the new code follow the evidence of the uses it falls under, did it bring in vendored packages or imitated mechanisms the map does not record, and do the guides it affects still hold. Vendor alignment only; general bugs belong to a code review.",
45604
- content: "---\nname: review\ndescription: Review the current branch's changes against the map — the health check narrowed to the files the branch touched: does the new code follow the evidence of the uses it falls under, did it bring in vendored packages or imitated mechanisms the map does not record, and do the guides it affects still hold. Vendor alignment only; general bugs belong to a code review.\n---\n\n# review the branch\n\nThe health check, narrowed to what this branch changed. Load `vendy skills get health` for the judgments; this workflow says only what is different.\n\n## 1. The changes\n\nEvery file changed since the merge-base with the base branch — main unless the user says otherwise — committed or not.\n\n## 2. The uses they fall under\n\nRun `vendy check`, then match every changed file against the map: every project-wide use applies to all of them, and a scoped use applies to the files its globs match and its `!` globs do not. A changed file under no use is still read — it is where unmapped findings come from.\n\n## 3. Judge the changed lines\n\nHealth's step 3, on the changed lines and what they call, not the whole scope:\n\n- **Deviation** — the new code against its uses' evidence.\n- **Unmapped** — a new import of a vendored package outside every scope, or new code imitating a reference repo with no use recording it.\n- **Not worth a repo** — the branch vendored a library that health would flag as not worth one.\n- **Stale map** — the branch moved or deleted what a scope covered, or changed a feature's role without changing its use.\n- **Guide** — a guide whose use the branch changed, now out of date.\n\nThe fix for an unmapped or stale finding is usually an align the branch skipped: say so.\n\n## 4. Report, then fix\n\nReport as health's step 4 does, findings only for this branch. Fix what the user picks.\n"
45603
+ description: "Review the current branch's changes against the map — the health check narrowed to the files the branch touched. Does the new code follow the evidence of the uses it falls under, did it bring in vendored packages or imitated mechanisms the map does not record, and do the guides it affects still hold? Vendor alignment only; general bugs belong to a code review.",
45604
+ content: "---\nname: review\ndescription: Review the current branch's changes against the map — the health check narrowed to the files the branch touched. Does the new code follow the evidence of the uses it falls under, did it bring in vendored packages or imitated mechanisms the map does not record, and do the guides it affects still hold? Vendor alignment only; general bugs belong to a code review.\n---\n\n# review the branch\n\nThe health check, narrowed to what this branch changed. Load `vendy skills get health` for the judgments; this workflow says only what is different.\n\n## 1. The changes\n\nEvery file changed since the merge-base with the base branch — main unless the user says otherwise — committed or not.\n\n## 2. The uses they fall under\n\nRun `vendy check`, then match every changed file against the map: every project-wide use applies to all of them, and a scoped use applies to the files its globs match and its `!` globs do not. A changed file under no use is still read — it is where unmapped findings come from.\n\n## 3. Judge the changed lines\n\nHealth's step 3, on the changed lines and what they call, not the whole scope:\n\n- **Deviation** — the new code against its uses' evidence.\n- **Unmapped** — a new import of a vendored package outside every scope, or new code imitating a reference repo with no use recording it.\n- **Not worth a repo** — the branch vendored a library that health would flag as not worth one.\n- **Stale map** — the branch moved or deleted what a scope covered, or changed a feature's role without changing its use.\n- **Guide** — a guide whose use the branch changed, now out of date.\n\nThe fix for an unmapped or stale finding is usually an align the branch skipped: say so.\n\n## 4. Report, then fix\n\nReport as health's step 4 does, findings only for this branch. Fix what the user picks.\n"
45605
45605
  },
45606
45606
  "setup": {
45607
45607
  description: "Bring vendy into a project and decide how it behaves — which agents get session hooks, and editor exclusions. Also covers what setup writes into AGENTS.md, and changing any of it later.",
@@ -46212,7 +46212,7 @@ const withGitSeparator = (args) => {
46212
46212
  const run = (args, config) => runWith(vendy, config)(withGitSeparator(args)).pipe(provideService(Blocking, (description) => error(`waiting for file lock on ${description}`)), provideService(runner, invocation(process.cwd())), provideService(CliConfig, cliConfig), provideService(Formatter, formatter));
46213
46213
  //#endregion
46214
46214
  //#region src/main.ts
46215
- const version = "0.1.1";
46215
+ const version = "0.1.2";
46216
46216
  const isSqliteExperimentalWarning = (warning) => warning.name === "ExperimentalWarning" && warning.message.startsWith("SQLite ");
46217
46217
  for (const printWarning of process.listeners("warning")) {
46218
46218
  process.off("warning", printWarning);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zebeqo/vendy",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Let your coding agent choose, build with, and maintain vendored repos, and keep your code in step as upstream moves",
5
5
  "license": "MIT",
6
6
  "repository": {