liteagents 3.0.0 → 3.5.0

package/packages/ampcode/{commands → skills}/remember/stub-check.cjs

@@ -60,31 +60,40 @@ function lexists(p) {
  * "the file is absent" and is still followed on write — or any parent
  * directory may be a link pointing elsewhere. This runs across a whole fleet
  * of repos, so a relative link only has to reach a sibling checkout.
+ *
+ * A link that stays INSIDE the repo is not an escape: a repo that keeps its
+ * rules or its config behind an in-repo symlink is an ordinary setup, and
+ * refusing it would strand that repo forever. So the leaf is followed by hand
+ * with readlink — which works on a dangling link, where realpath cannot — and
+ * each hop re-resolves the parents, because the file a link points at can sit
+ * behind a linked directory of its own.
  */
 function escapesRepo(repo, target) {
   let root;
   try { root = fs.realpathSync(repo); } catch (e) { return true; }
 
-  // Walk up to the deepest ancestor that exists; anything below it cannot be
-  // a link yet, so only the existing part needs resolving.
-  const tail = [];
-  let dir = path.dirname(target);
-  while (!lexists(dir)) {
-    tail.unshift(path.basename(dir));
-    const up = path.dirname(dir);
-    if (up === dir) return true;                  // walked off the filesystem root
-    dir = up;
-  }
-
-  let resolved;
-  try { resolved = path.join(fs.realpathSync(dir), ...tail, path.basename(target)); }
-  catch (e) { return true; }                      // an ancestor is a dangling link
-
-  // The last component can be a link even when every directory above it is
-  // clean — that is the dangling-file case.
-  try { if (fs.lstatSync(resolved).isSymbolicLink()) return true; } catch (e) { /* absent: fine */ }
+  let p = path.resolve(target);
+  for (let hop = 0; hop < 40; hop++) {
+    // Resolve the existing part of the path. Walk up to the deepest ancestor
+    // that exists; anything below it cannot be a link yet.
+    const tail = [];
+    let dir = path.dirname(p);
+    while (!lexists(dir)) {
+      tail.unshift(path.basename(dir));
+      const up = path.dirname(dir);
+      if (up === dir) return true;                  // walked off the filesystem root
+      dir = up;
+    }
+    try { p = path.join(fs.realpathSync(dir), ...tail, path.basename(p)); }
+    catch (e) { return true; }                      // an ancestor is a dangling link
 
-  return resolved !== root && !resolved.startsWith(root + path.sep);
+    let to;
+    try { to = fs.readlinkSync(p); } catch (e) {
+      return p !== root && !p.startsWith(root + path.sep);   // not a link: decide here
+    }
+    p = path.resolve(path.dirname(p), to);
+  }
+  return true;                                      // a link cycle: refuse
 }
 
 /** Index range of the lines strictly between a marker pair, or null. */

package/packages/ampcode/{commands → skills}/remember/sync-rules.cjs

@@ -50,31 +50,40 @@ function lexists(p) {
  * "the file is absent" and is still followed on write — or any parent
  * directory may be a link pointing elsewhere. This runs across a whole fleet
  * of repos, so a relative link only has to reach a sibling checkout.
+ *
+ * A link that stays INSIDE the repo is not an escape: a repo that keeps its
+ * rules or its config behind an in-repo symlink is an ordinary setup, and
+ * refusing it would strand that repo forever. So the leaf is followed by hand
+ * with readlink — which works on a dangling link, where realpath cannot — and
+ * each hop re-resolves the parents, because the file a link points at can sit
+ * behind a linked directory of its own.
  */
 function escapesRepo(repo, target) {
   let root;
   try { root = fs.realpathSync(repo); } catch (e) { return true; }
 
-  // Walk up to the deepest ancestor that exists; anything below it cannot be
-  // a link yet, so only the existing part needs resolving.
-  const tail = [];
-  let dir = path.dirname(target);
-  while (!lexists(dir)) {
-    tail.unshift(path.basename(dir));
-    const up = path.dirname(dir);
-    if (up === dir) return true;                  // walked off the filesystem root
-    dir = up;
-  }
-
-  let resolved;
-  try { resolved = path.join(fs.realpathSync(dir), ...tail, path.basename(target)); }
-  catch (e) { return true; }                      // an ancestor is a dangling link
-
-  // The last component can be a link even when every directory above it is
-  // clean — that is the dangling-file case.
-  try { if (fs.lstatSync(resolved).isSymbolicLink()) return true; } catch (e) { /* absent: fine */ }
+  let p = path.resolve(target);
+  for (let hop = 0; hop < 40; hop++) {
+    // Resolve the existing part of the path. Walk up to the deepest ancestor
+    // that exists; anything below it cannot be a link yet.
+    const tail = [];
+    let dir = path.dirname(p);
+    while (!lexists(dir)) {
+      tail.unshift(path.basename(dir));
+      const up = path.dirname(dir);
+      if (up === dir) return true;                  // walked off the filesystem root
+      dir = up;
+    }
+    try { p = path.join(fs.realpathSync(dir), ...tail, path.basename(p)); }
+    catch (e) { return true; }                      // an ancestor is a dangling link
 
-  return resolved !== root && !resolved.startsWith(root + path.sep);
+    let to;
+    try { to = fs.readlinkSync(p); } catch (e) {
+      return p !== root && !p.startsWith(root + path.sep);   // not a link: decide here
+    }
+    p = path.resolve(path.dirname(p), to);
+  }
+  return true;                                      // a link cycle: refuse
 }
 
 function templatePath() {

package/packages/{claude/commands → ampcode/skills}/remember/version-check.cjs

@@ -79,7 +79,7 @@ function versionFromPackageJson() {
 }
 
 // The installer stamps the release it wrote into <install root>/manifest.json.
-// version-check.cjs sits at <root>/<commands|command>/remember/, so the root is
+// version-check.cjs sits at <root>/<skills|commands|command>/remember/, so the root
 // two levels up. This is the fast path: reading a file beats spawning npm.
 function versionFromManifest() {
   try {

package/packages/ampcode/skills/root-cause/SKILL.md

@@ -0,0 +1,220 @@
+---
+name: root-cause
+description: Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time
+allowed-tools: Read, Grep, Glob
+---
+
+# Root Cause
+
+**Find the cause before you change any code.**
+
+## The Law
+
+```
+NO FIX WITHOUT A CAUSE YOU CAN POINT AT
+```
+
+A fix at the place the error *appeared* is a symptom fix. It is a failure even when
+the symptom goes away, because the real cause is still there and will surface
+somewhere else, later, with less context.
+
+You cannot propose a fix until Phase 1 is done.
+
+## When to Use
+
+Any technical issue: a failing test, a production bug, unexpected behaviour, a
+performance problem, a broken build, an integration that will not talk.
+
+**Especially when it feels like overkill:**
+- Under time pressure — emergencies are exactly when guessing is most tempting and most expensive
+- "Just one quick fix" looks obvious
+- You have already tried a fix and it did not work
+- You do not fully understand the issue
+
+Simple bugs have root causes too, and finding one takes minutes. Guess-and-check
+takes hours and leaves damage behind.
+
+---
+
+## Phase 1 — Gather Evidence
+
+Do all of this **before** forming any opinion about the fix.
+
+### 1. Read the error completely
+
+Do not skim past it. Read the whole message, the whole stack trace, every warning
+above it. Note line numbers, file paths, error codes. The answer is often written
+there in full.
+
+### 2. Reproduce it consistently
+
+Can you trigger it on demand? What are the exact steps? Does it happen every time?
+
+If it is not reproducible, gather more data. Do not start guessing — an
+intermittent bug you cannot trigger is a bug you cannot prove you fixed.
+
+### 3. Check what changed
+
+Recent commits, the working diff, new dependencies, config edits, environment
+differences between the place it works and the place it does not.
+
+Be careful here: the most recent change is the most *available* suspect, not the
+most likely one. Recency is a lead to test, never a conclusion.
+
+### 4. Instrument the boundaries (multi-component systems)
+
+When the path crosses components — CI → build → sign, API → service → database,
+workflow → script → tool — do not reason about where it breaks. Measure it.
+
+For each boundary, log what goes **in** and what comes **out**, and confirm
+configuration and environment actually propagated across it.
+
+```bash
+echo "=== layer 1: is the secret present in the workflow? ==="
+echo "IDENTITY: ${IDENTITY:+SET}${IDENTITY:-UNSET}"
+
+echo "=== layer 2: did it survive into the build script? ==="
+env | grep IDENTITY || echo "IDENTITY not in environment"
+
+echo "=== layer 3: what does the tool actually see? ==="
+security find-identity -v
+```
+
+Run it **once** to find which boundary fails, then investigate only that
+component. This turns "somewhere in the pipeline" into a named layer.
+
+### 5. Trace the bad value back to where it was born
+
+When the error surfaces deep in the call stack, the place it exploded is almost
+never the place it went wrong. Walk backwards.
+
+**The chain:**
+
+1. **Observe the symptom** — `git init` ran in the source directory
+2. **Find the immediate cause** — the code that directly did it:
+   `execFileAsync('git', ['init'], { cwd: projectDir })`
+3. **Ask what called this, and with what value** — `projectDir` was `''`, and an
+   empty `cwd` silently resolves to the process's own directory
+4. **Keep going up** — who passed the empty string? and who gave it to *them*?
+5. **Stop at the origin** — the point where a correct value first became wrong
+
+Fix it **there**. Then, if the value is dangerous, validate it at each layer on
+the way down as well, so the same mistake cannot recur through a different path.
+
+**When you cannot trace it by reading, instrument it:**
+
+```typescript
+async function gitInit(directory: string) {
+  console.error('DEBUG git init:', {
+    directory,
+    cwd: process.cwd(),
+    stack: new Error().stack,
+  });
+  await execFileAsync('git', ['init'], { cwd: directory });
+}
+```
+
+- Capture the **stack**, not just the value — it names the caller you are looking for
+- Log **before** the dangerous operation, not in its failure handler
+- Include surrounding context: the directory, the working directory, relevant environment
+- In tests, write to standard error directly; a project logger may be suppressed
+
+**When something pollutes a test run but you cannot tell which test:** bisect.
+Run the tests one at a time and stop at the first one that leaves the mess behind.
+`find-polluter.sh` in this skill's directory does exactly that.
+
+---
+
+## Phase 2 — Compare Against Something That Works
+
+You are looking for a difference, and the fastest way to see one is a side-by-side.
+
+- **Find a working example** — similar code in the same codebase that behaves correctly
+- **Read the reference completely** if you are following a pattern. Every line. Skimming a
+  reference and adapting "the idea" is how half-understood patterns ship
+- **List every difference**, however small. Do not filter by "that can't matter" — that
+  judgement is exactly what you do not have yet
+- **Check the dependencies**: what config, what environment, what other components does
+  the working one have that the broken one does not?
+
+---
+
+## Phase 3 — One Hypothesis, One Variable
+
+- **State it in writing:** "I think X is the cause, because Y." Specific, not vague.
+- **Test it with the smallest possible change.** One variable. A controlled test that
+  isolates your suspect beats a plausible story about the most recent commit.
+- **Read the result honestly.** Confirmed → Phase 4. Not confirmed → form a *new*
+  hypothesis. Never stack a second fix on top of an unconfirmed first one.
+- **Say when you do not know.** "I don't understand why X happens" is a real state and a
+  useful thing to report. Pretending to know produces confident wrong fixes.
+
+---
+
+## Phase 4 — Fix at the Source
+
+### 1. Write the failing test first
+
+The simplest reproduction you can manage — an automated test if there is a suite, a
+throwaway script if there is not.
+
+**Run it against the unfixed code and watch it fail, for the reason you expect.** A
+test written after the fix, or one that passes both before and after, proves nothing.
+This is the step that converts your hypothesis into evidence.
+
+### 2. Make one change
+
+Fix the cause you identified. One change. No "while I'm here" improvements, no bundled
+refactoring — those make it impossible to tell what actually worked.
+
+### 3. Verify
+
+Does the new test pass? Does the rest of the suite still pass? Is the original symptom
+actually gone — checked, not assumed?
+
+### 4. If the fix did not work, stop and count
+
+Under three attempts: return to Phase 1 with what you just learned. The failed attempt
+is evidence.
+
+**Three or more failed fixes means you have the wrong model of the problem.** Do not
+attempt a fourth. The pattern to watch for: each fix uncovers a new problem somewhere
+else, or each one needs "just a bit of refactoring" to land.
+
+That is an architecture question, not a hypothesis question. Stop and raise it.
+
+---
+
+## Red Flags — Stop and Return to Phase 1
+
+- "Quick fix now, investigate later"
+- "Just try changing X and see"
+- Several changes at once, then run the tests
+- "Skip the test, I'll check it by hand"
+- "It's probably X" — probably is not a cause
+- "I don't fully understand this, but this might work"
+- Listing fixes before tracing where the bad value came from
+- "One more attempt" when two have already failed
+- Each fix revealing a new problem somewhere else
+
+## Quick Reference
+
+| Phase | You do | Done when |
+|---|---|---|
+| **1. Evidence** | Read the error, reproduce, check changes, instrument boundaries, trace the value back | You can say what happened and where it started |
+| **2. Compare** | Find a working case, read it fully, list every difference | You know what is different |
+| **3. Hypothesis** | State one cause, test one variable | Confirmed, or you have a new hypothesis |
+| **4. Fix** | Failing test first, one change, verify | The test that failed now passes, and nothing else broke |
+
+## When There Really Is No Root Cause
+
+It happens — a genuine race, an upstream bug, a hardware fault. But roughly nineteen
+times in twenty, "no root cause" means the investigation stopped early.
+
+Before you conclude it: can you reproduce it? Did you instrument every boundary? Did
+you trace the value to its origin, or only to the last function you recognised?
+
+## Related
+
+- **AGENT_RULES.md → Testing Standards** — what makes the Phase 4 test a real one
+- **`/test-generate`** — build out the suite once the cause is fixed

package/packages/{claude/commands/security.md → ampcode/skills/security/SKILL.md}

@@ -1,9 +1,9 @@
 ---
 name: security
 description: Security audit — recurring six, injection, auth, trust boundaries
-usage: /security
 argument-hint: [file, directory, or leave empty for full scan]
 allowed-tools: Read, Grep, Glob, Bash(git log:*), Bash(git grep:*), Bash(rg:*)
+disable-model-invocation: true
 ---
 Audit $ARGUMENTS for security vulnerabilities. **Reports, never edits** — it
 verifies every claim, then hands the findings to whoever asked.

package/packages/{claude/commands/ship.md → ampcode/skills/ship/SKILL.md}

@@ -1,8 +1,8 @@
 ---
 name: ship
 description: Mechanical pre-deploy gate — tests, build, tree state
-usage: /ship
 allowed-tools: Read, Grep, Glob, Bash(git:*), Bash(npm:*), Bash(pnpm:*), Bash(yarn:*), Bash(pytest:*), Bash(python:*), Bash(go:*), Bash(cargo:*), Bash(make:*)
+disable-model-invocation: true
 ---
 Mechanical pre-deploy / pre-merge gate. Every item here is answerable by
 **running a command** and reading its exit code — no code judgment. Code

package/packages/ampcode/skills/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/packages/ampcode/{commands/skill-creator.md → skills/skill-creator/SKILL.md}

@@ -1,9 +1,8 @@
 ---
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
-usage: /skill-creator <skill-type> <skill-description>
-auto_trigger: false
 license: Complete terms in LICENSE.txt
+allowed-tools: Read, Grep, Glob
 ---
 
 # Skill Creator

package/packages/ampcode/{commands/stash.md → skills/stash/SKILL.md}

@@ -1,8 +1,9 @@
 ---
 name: stash
 description: Stash session context [name]
-usage: /stash ["optional-name"]
 argument-hint: [optional stash name]
+allowed-tools: Read, Grep, Glob
+disable-model-invocation: true
 ---
 
 Save session context for compaction recovery or handoffs.

package/packages/{claude/commands/test-generate.md → ampcode/skills/test-generate/SKILL.md}

@@ -1,9 +1,9 @@
 ---
 name: test-generate
 description: Generate and run tests [file]
-usage: /test-generate <file>
 argument-hint: [file or symbol to test]
 allowed-tools: Read, Edit, Write, Grep, Glob, Bash(npm test:*), Bash(npx jest:*), Bash(npx vitest:*), Bash(pnpm test:*), Bash(yarn test:*), Bash(pytest:*), Bash(python:*), Bash(go test:*), Bash(cargo test:*), Bash(make test:*)
+disable-model-invocation: true
 ---
 Generate tests for $ARGUMENTS, then run them. This is a generate → run →
 verify loop, not just file generation.
@@ -28,7 +28,7 @@ Match existing patterns:
   or new test-runner config.
 - Do **not** add test-only public methods or exports to production code to
   make a test possible — if the test wants a hook the prod code doesn't
-  expose, stop and ask (`test-traps` territory).
+  expose, stop and ask.
 
 ## 3. Run
 Execute the project's real test command, scoped to just the new tests

package/packages/ampcode/variants.json

@@ -1,8 +1,8 @@
 {
   "pro": {
     "name": "Pro",
-    "description": "Complete installation with all agents and commands",
+    "description": "Complete installation with all agents and skills",
     "agents": "*",
-    "commands": "*"
+    "skills": "*"
   }
 }