@happyvertical/smrt-dev-mcp 0.60.9 → 0.60.11

package/skills/smrt-catalog/evals.json

@@ -0,0 +1,28 @@
+{
+  "skill": "smrt-catalog",
+  "note": "Trigger eval set. A harness (or a reviewer) runs each prompt in a consumer project that depends on smrt packages and checks whether the skill fires. src/agent-skills.test.ts asserts the description covers every positive signal class.",
+  "positive": [
+    { "prompt": "add a nightly cleanup job", "signal": "jobs" },
+    { "prompt": "retry failed webhook deliveries with backoff", "signal": "jobs" },
+    { "prompt": "send the customer a receipt email", "signal": "email" },
+    { "prompt": "notify the owner when an invoice is overdue", "signal": "email" },
+    { "prompt": "upload the logo to storage", "signal": "storage" },
+    { "prompt": "let users attach PDFs to a ticket", "signal": "storage" },
+    { "prompt": "make this tenant-aware", "signal": "tenancy" },
+    { "prompt": "scope these records per organization", "signal": "tenancy" },
+    { "prompt": "add a price field", "signal": "money" },
+    { "prompt": "store the refund amount and currency", "signal": "money" },
+    { "prompt": "require a manager to approve discounts", "signal": "approvals" },
+    { "prompt": "record who changed each order and when", "signal": "audit" },
+    { "prompt": "generate a PDF invoice", "signal": "documents" }
+  ],
+  "negative": [
+    { "prompt": "rename the Article title label to Headline", "reason": "ordinary change inside an existing @smrt() object" },
+    { "prompt": "add a unit test for Order.total()", "reason": "tests of an existing object" },
+    { "prompt": "validate that Product.slug is lowercase", "reason": "validation inside an existing object" },
+    { "prompt": "fix the off-by-one in the pagination component", "reason": "UI bug, no new plumbing" },
+    { "prompt": "add a description text field to Customer", "reason": "plain field on an existing object" },
+    { "prompt": "explain what the Invoice class does", "reason": "read-only question" },
+    { "prompt": "bump vitest to the latest minor", "reason": "tooling" }
+  ]
+}

package/skills/smrt-contribute/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: smrt-contribute
+description: Use when working in a fork or clone of the happyvertical/smrt repository as an outside contributor, for example "fix a bug in smrt-jobs and open a PR", "contribute this change upstream", or "add docs to smrt-core". Gives the fork pull-request procedure from CONTRIBUTING.md and the traps that fail from outside (package-name test filters, format then lint, generated knowledge pages, PR title length, no changesets, fork CI approval). Do not use in a project that merely depends on smrt packages (use smrt-catalog), or in a maintainer session where the control-plane skills (implement, claim-issue, review-cycle, ship) are installed.
+---
+
+# SMRT Contribute
+
+Procedure for contributing to `happyvertical/smrt` from a fork or clone. It
+is `CONTRIBUTING.md` as steps. The maintainer lifecycle in
+`AGENTS.md` (claim labels, dispatch labels, patch trains, `hv-agent-run`
+blocks, `implement`, `review-cycle`) does not apply to you: you cannot claim
+issues and the skills live in a private repository. Do not try to load them.
+
+You submit the PR, so read and understand every line of it before opening it.
+
+## Procedure
+
+1. **Scope.** One concern per PR. For anything bigger than a focused bug fix,
+   or for changes to core decorators, the scanner or schema generation,
+   dependencies, new packages, or `.github/`, open or comment on an issue first.
+2. **Orient.** Read `AGENTS.md` and the affected package's `AGENTS.md`
+   (non-obvious invariants and extra checks). Use Node and pnpm versions from
+   `package.json`.
+3. **Setup.** `pnpm install` then `pnpm build`; packages consume each other's
+   built output, so build once in a fresh clone.
+4. **Branch** in your fork, off `main`. Target `main` with the PR.
+5. **Change.** Add a regression test for a bug fix and tests for new behaviour
+   (`TESTING_STANDARD.md`). Update the package README for user-facing behaviour.
+6. **Test by package name:** `pnpm --filter @happyvertical/smrt-jobs test`.
+   Directories under `packages/` drop the `smrt-` prefix, and a filter that
+   matches no package exits 0 having run nothing. Confirm tests actually ran.
+7. **Format, then lint:** `pnpm format` then `pnpm lint`.
+8. **Generated pages.** When a package manifest, an `AGENTS.md`, an intent or a
+   playbook changed, run `pnpm knowledge:check --strict --format markdown` and
+   `pnpm knowledge:okf`, and commit the regenerated pages (they are checked in).
+   Keep root `AGENTS.md` chain under the 32 KB cap: `pnpm check:agents-chain`.
+9. **Commit** with conventional commits (`fix(core): preserve tenant scope`).
+   Never author `.changeset/*.md`; release automation writes them.
+10. **Open the PR** against `main`. Title: conventional form, at most 92
+    characters (the squash appends ` (#N)` and the commit header limit is 100).
+
+## Never
+
+- `--no-verify`, skipping a hook, disabling a gate, or pinning around a failure.
+  If a documented command cannot run as documented, say so in the PR instead
+  of working around it.
+- Touching `.github/`. The **Fork Workflow Change Guard** fails any fork PR
+  that changes it; a maintainer re-lands such changes from the main repository.
+- Claiming issues, adding claim or dispatch labels, or adding `hv-agent-run`
+  blocks.
+
+## CI on a fork PR
+
+- A maintainer must approve the **Fork PR Validation** run before it executes.
+- Until then `Required CI` and `postgres-required` fail with "awaiting
+  maintainer approval". That is expected; do not try to fix it.
+- A maintainer applies `ci: fork-approved` after reviewing and approving the
+  head commit. A new push removes the label and needs a fresh approval.
+- If a maintainer's approval was refused, they must remove and re-add the
+  label; re-adding a label that is already present fires no event.
+
+## PR description
+
+Include:
+
+- the behaviour change (what and why);
+- how it was validated (commands run, with results);
+- which package `AGENTS.md` invariants it touches, or "none".
+
+## Upstream gaps found from a consumer project
+
+If you arrived here because a consumer project needed behaviour an smrt package
+lacks, link the originating issue or use case in the PR description.

package/skills/smrt-contribute/evals.json

@@ -0,0 +1,18 @@
+{
+  "skill": "smrt-contribute",
+  "note": "Trigger eval set. Positive: an outside contributor in a fork or clone of happyvertical/smrt. Negative: a consumer project, or a maintainer session with the control-plane skills. src/agent-skills.test.ts asserts the description covers the positive and negative contexts.",
+  "positive": [
+    { "prompt": "fix a bug in smrt-jobs and open a PR", "context": "fork" },
+    { "prompt": "I cloned happyvertical/smrt; add docs for smrt-core to the README", "context": "clone" },
+    { "prompt": "contribute this change upstream to smrt", "context": "fork" },
+    { "prompt": "open a pull request against happyvertical/smrt from my fork", "context": "fork" },
+    { "prompt": "what do I need to run before sending a PR to smrt?", "context": "clone" }
+  ],
+  "negative": [
+    { "prompt": "add a nightly cleanup job", "context": "consumer project that depends on smrt packages" },
+    { "prompt": "make the Invoice model tenant-aware", "context": "consumer project that depends on smrt packages" },
+    { "prompt": "implement issue #4123", "context": "maintainer session with implement and claim-issue skills" },
+    { "prompt": "run review-cycle and ship the PR", "context": "maintainer session with control-plane skills" },
+    { "prompt": "fix the failing test in my app", "context": "unrelated repository" }
+  ]
+}