@atlassian/chippy 0.0.0-stage → 0.0.1-beta.2

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 (c) 2026 Atlassian US., Inc.
+
+   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/README.md

@@ -1,3 +1,277 @@
-# Temporary Holding Version
+![Chippy logo](https://raw.githubusercontent.com/atlassian-labs/chippy/main/.agents/skills/chippy/extension/icon-48.png)
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+# Chippy
+
+[![Atlassian license](https://img.shields.io/badge/license-Apache%202.0-blue.svg?style=flat-square)](https://github.com/atlassian-labs/chippy/blob/main/LICENSE) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](https://github.com/atlassian-labs/chippy/blob/main/CONTRIBUTING.md)
+
+**A friend who helps you understand what’s happening, find the cause, and fix it.**
+
+<p align="center">
+  <a href="assets/chippy-intro.mp4"><img src="assets/chippy-intro.svg" width="900" alt="Animated intro: Chippy connects your coding agent to the running React page through React's DevTools hook, traces a button to its component, owners, and source line, runs experiments on live state, separates a slow click's trigger from the busiest component, and shows the browser scripts, local helper, and agent skill working as one system."></a>
+  <br><a href="assets/chippy-intro.mp4">Watch with sound</a>
+</p>
+
+Chippy lets your coding agent see the React app running in your browser: which
+component drew an element, its props and state, where it lives in source, and
+what re-rendered during a slow interaction. Ask the agent, or point at an element
+on the page and leave it a note.
+
+Chippy works with standard React and needs no patched packages. Development
+builds give the most detail; production builds show less, and every answer says
+what was available. See [React compatibility](https://github.com/atlassian-labs/chippy/blob/main/docs/react-compatibility.md).
+
+## What you can ask
+
+- **Explore:** "Which components render this list, and what state do they hold?"
+- **Debug:** "Where does this label's text come from?" or "Which boundary shows this spinner?"
+- **Compare:** "What changed in the tree between these two states, or these two pages?"
+- **Investigate:** "Why is this click slow?" or "What re-renders on initial load?"
+
+## Install
+
+Chippy has three parts:
+
+- The **agent skill** tells your coding agent how to run Chippy.
+- The **local helper** is a small server on `127.0.0.1:7823`. The agent starts
+  it when it needs it.
+- The **page runtime** runs inside the page and reads React.
+
+The skill and the helper are the same in every setup. You choose how the page
+runtime gets into the page; see [Connect a page](#connect-a-page).
+
+You need Node.js 22.20 or later, which the skills CLI requires.
+
+1. Install the agent skill with the [skills CLI](https://github.com/vercel-labs/skills):
+
+   ```sh
+   npx skills add atlassian-labs/chippy --skill chippy -g
+   ```
+
+   Choose your coding agents when it asks, or name them with `-a`, for example
+   `-a claude-code`. With `-g`, every project can use the skill, and its files
+   live in `~/.agents/skills/chippy`; each agent's skills folder links to that
+   copy. Leave out `-g` to install it in the current project's
+   `.agents/skills/chippy` instead. Run `npx skills update chippy` to update it.
+
+2. Connect a page with one of the routes in [Connect a page](#connect-a-page).
+
+3. Ask your agent to use Chippy on the page.
+
+The agent runs Chippy through the skill's `chippy.sh` script, which needs bash
+(macOS, Linux, or WSL on Windows). You don't start anything yourself: the agent
+starts a local helper on `127.0.0.1:7823` when it needs one. A sandboxed agent
+asks for permission to reach it; approve the prompt or allow `chippy.sh`. If
+your agent runs in a container or on a remote machine, the browser must reach
+the helper's port through an SSH tunnel, a published container port, or other
+forwarding your environment provides; Chippy does not set that up.
+[Local and wide binds](https://github.com/atlassian-labs/chippy/blob/main/docs/trust-boundary.md#local-and-wide-binds)
+lists what to set for each setup.
+
+**Optional: connect over MCP.** If your agent supports MCP, it can call Chippy
+as tools instead of running a script. Ask it:
+
+> Connect Chippy over MCP using the MCP setup steps in the Chippy skill.
+
+The agent adds the Chippy server to its own MCP configuration and checks the
+connection. Some agents need a restart before the new tools appear. To set it
+up yourself, see [MCP setup](https://github.com/atlassian-labs/chippy/blob/main/.agents/skills/chippy/references/mcp.md).
+
+## Connect a page
+
+Every route loads the same page runtime and talks to the same helper. The
+routes differ in what you set up, whether Chippy stays after a reload, and
+whether Chippy can record the initial page load.
+
+| Route | What you set up | After a reload | Records the initial load |
+| --- | --- | --- | --- |
+| [Browser extension](#browser-extension) | Load the extension once, then enable it for each site | Chippy loads again | Yes |
+| [Agent-driven browser](#agent-driven-browser) | Nothing. The agent opens its own Playwright browser | Chippy loads again | Yes, when the agent loads Chippy before the page |
+| [Local proxy](#local-proxy) | Nothing. The agent starts the proxy, and you open the proxy address | Chippy loads again | Yes |
+| [Storybook addon](#storybook-addon) | Add the addon to your Storybook configuration | Chippy remounts the story and stays | The story's mount |
+| [Console import](#console-import) | Paste one line into the page's console | Chippy is removed. Paste the line again | No |
+| [Your app's code](#your-apps-code) | Install the npm package and call `connectChippy()` | Call it again | No |
+
+"Records the initial load" means that the agent can reload the page and record
+the renders from the first commit. Every route records renders that happen
+after Chippy connects.
+
+### Browser extension
+
+Use the extension for day-to-day work in your own Chrome or Chromium browser.
+
+1. Open `chrome://extensions`, turn on **Developer mode**, and choose
+   **Load unpacked**. Select the skill's `extension` folder:
+   `~/.agents/skills/chippy/extension`, or `.agents/skills/chippy/extension`
+   in your project if you installed without `-g`. The folder picker hides
+   folders whose names start with a dot, so type the path instead of browsing.
+   On macOS, press **Cmd+Shift+G**, paste the path, press **Return**, and
+   choose **Select**. On Linux, press **Ctrl+L** and paste the path. On
+   Windows, paste it into the address bar. After `npx skills update`, click
+   **Reload** on the Chippy card in `chrome://extensions`.
+2. Open your app, click the Chippy extension icon, and enable Chippy for the
+   page's origin.
+
+### Agent-driven browser
+
+The agent opens a Playwright browser, loads Chippy into the page, and drives
+the page itself. No extension is needed. Use this route for repeatable flows,
+headless checks, and CI. Ask your agent to open the page with Chippy in
+Playwright; the skill has the setup steps.
+
+### Local proxy
+
+The helper can sit in front of a dev server on your machine and add Chippy to
+the page before the page's own scripts run. No extension is needed, and this
+route works in any browser, including one that your agent drives. Ask your
+agent to start the Chippy proxy for your page, then open the address that it
+gives you on `127.0.0.1:7823`. The proxy forwards only to servers on this
+machine, and it adds Chippy only to the page address that the agent gave it.
+It removes the page's Content Security Policy headers, so it also works for
+pages that block the console import.
+
+### Storybook addon
+
+In Storybook 10.3 or later, add the addon to your Storybook configuration:
+
+```js
+export default {
+  addons: ['@atlassian/chippy/storybook'],
+};
+```
+
+The addon adds Chippy panels to Storybook and connects each story to your agent.
+When the agent reloads the page, Storybook remounts the current story instead of
+reloading the preview. See the
+[package documentation](https://github.com/atlassian-labs/chippy/blob/main/docs/npm-package.md#storybook)
+for build targets.
+
+### Console import
+
+Use this for a quick look at a page where you cannot install the extension.
+Once the agent has started the helper, paste this into the page's console:
+
+```js
+import('http://127.0.0.1:7823/__chippy/inject.mjs')
+```
+
+A reload removes Chippy, so paste the line again after every reload or
+navigation. Sites with a strict Content Security Policy block the import.
+
+### Your app's code
+
+For pages that the extension cannot reach, such as an embedded browser, call
+`connectChippy()` from `@atlassian/chippy/browser` in the page. It loads the
+same runtime as the console import. See
+[Connect a browser page to an agent](https://github.com/atlassian-labs/chippy/blob/main/docs/npm-package.md#connect-a-browser-page-to-an-agent).
+
+## Ask the agent, or point at the page
+
+- **Ask the agent** about the page. It finds components by name, text, test ID,
+  source file, or prop, reads their state, clicks through the page, and records
+  renders.
+- **Point at the page:** click the Chippy button in the page corner and drag a
+  probe marker (P1, or P2 to compare two elements) onto an element. Choose
+  whether you want it explained, investigated, or changed, and add a note. Then
+  ask the agent to read it, or to keep watching for new notes while you click
+  around. The extension, the local proxy, and the Storybook addon show the
+  Chippy button. The console import does not.
+
+<p align="center">
+  <a href="assets/chippy-call.mp4"><img src="assets/chippy-call.svg" width="900" alt="Animated clip: the asks roll in and Jira keeps them in line, so you call a chippy. Chippy gives your coding agent a hand in the running app: it finds the component and source line for a button to move, reads live props and state to show why a button stays disabled, compares before and after, finds what set off a slow click, connects the page, React, and your code, and turns the page into an experimentation lab."></a>
+  <br><a href="assets/chippy-call.mp4">Watch with sound</a>
+</p>
+
+## Evidence, then edits
+
+The agent works from what actually rendered instead of guessing from a code
+search. Some deep inspections re-run a component's code; if your components have
+side effects during render, say so and the agent uses read-only inspection
+instead. Chippy changes your source only when you ask it to, and checks the fix
+against the same page.
+
+## Use Chippy without an agent
+
+The `@atlassian/chippy` npm package also works with no agent, helper, or
+extension:
+
+- **Catch re-render regressions in tests.** Record which components rendered
+  during an interaction, and why, in a test or a script. Install the recorder in
+  your app's entry module before React DOM loads, and it records from the first
+  commit.
+- **Ship your own build** with extra plugins for your stack.
+
+See the [package documentation](https://github.com/atlassian-labs/chippy/blob/main/docs/npm-package.md) for setup.
+
+## How Chippy compares
+
+Other tools read what React already exposes, such as a component name or a
+source line, and hand it to a person or an agent. Chippy is a system of three
+parts that work together:
+
+- **In the browser,** Chippy walks React's fiber tree, owners, props, and hooks,
+  records commits during an interaction or page load, and can replay a
+  component's render to see how its hooks produced a value.
+- **The local helper** stores that evidence and gives the agent only what it
+  needs: compact summaries instead of raw trees, renders ranked by where a
+  cascade started, and diffs between snapshots of two states or two pages.
+- **The agent acts back on the page** at the React level, not only through
+  clicks: it finds fibers by name, text, test ID, file, or prop, forces a single
+  component to re-render, calls a component's callbacks directly, and records
+  what happens.
+
+| Tool | Built for | What it gives you | Where it stops |
+| --- | --- | --- | --- |
+| [React Developer Tools](https://react.dev/learn/react-developer-tools) | A person in DevTools | Component tree, props, state, hooks, and the Profiler | You read the panels and decide what to change |
+| [react-grab](https://www.react-grab.com/) | A person handing off to an agent | Hover an element and copy its component name, file and line, and HTML for your agent | Your agent takes it from the pasted context |
+| [react-scan](https://react-scan.com/) | A person watching the page | Render outlines, a toolbar showing what changed, and alerts on slow frames | Shows what is slow; finding the cause and fixing it is up to you |
+| [agent-browser](https://github.com/vercel-labs/agent-browser) | An agent driving a browser | Navigation, clicks, form input, snapshots, and screenshots | Works at the DOM and accessibility level, not inside React |
+| **Chippy** | An agent working from runtime evidence | Live React state, render recordings, and snapshot diffs, reduced for the agent, plus React-level actions on the page | Changes the source when you ask, then re-checks the same page |
+
+**Compared with react-grab.** Both start when you point at something on the
+page and the tool works out which React component it is. react-grab copies that
+context to your agent and its work is done. For Chippy, that is the first step.
+A probe resolves the owner chain, hooks, and props, so the agent can follow a
+value up the chain to the component that created it, past components that only
+pass it along. Two probes resolve to their nearest common parent. The agent then
+opens the source line, makes the change, and probes again to confirm it.
+
+**Compared with react-scan.** Both answer "what rendered, and why?" react-scan
+shows the answer on the page for a person to read. Chippy returns it as data for
+an agent to build on. Render recordings cover both a single interaction and the
+initial page load. The helper ranks them by where a render cascade started, not
+only by how long each component took, so the agent can tell the component that
+caused a slowdown from the ones that rendered along with it. The agent can then
+re-render a single component on purpose to test a fix, and record again to
+confirm the cascade is gone.
+
+**Compared with React Developer Tools.** Chippy reads the same information
+through React's DevTools hook and adds the steps a person would otherwise do by
+hand: tracing a value to where it comes from, replaying a render to explain a
+hook, comparing two states or pages, and separating the trigger of a slow
+interaction from collateral renders.
+
+**Compared with browser automation.** Tools such as agent-browser or Playwright
+operate the page as a user would: they click, type, and take screenshots. Chippy
+operates it from inside React and explains what React did in response. They work
+well together. The agent uses an automation tool to repeat a user flow and
+Chippy to inspect, nudge, and record the result, and keeps going until the
+change is verified.
+
+## Learn more
+
+- [Agent skill](https://github.com/atlassian-labs/chippy/blob/main/.agents/skills/chippy/SKILL.md) and its [references](https://github.com/atlassian-labs/chippy/blob/main/.agents/skills/chippy/references/README.md)
+- [React compatibility](https://github.com/atlassian-labs/chippy/blob/main/docs/react-compatibility.md)
+- [Plugins](https://github.com/atlassian-labs/chippy/blob/main/docs/plugins.md) for app-specific knowledge
+- [Trust boundary](https://github.com/atlassian-labs/chippy/blob/main/docs/trust-boundary.md): what page data Chippy sees and who can reach the helper
+- [Security policy](https://github.com/atlassian-labs/chippy/blob/main/SECURITY.md)
+- [Changelog](https://github.com/atlassian-labs/chippy/blob/main/CHANGELOG.md)
+
+To build, test, or change Chippy, see [Contributing](https://github.com/atlassian-labs/chippy/blob/main/CONTRIBUTING.md) and the
+[code of conduct](https://github.com/atlassian-labs/chippy/blob/main/CODE_OF_CONDUCT.md).
+
+## License
+
+Copyright (c) 2026 Atlassian US., Inc.
+Apache 2.0 licensed, see [LICENSE](https://github.com/atlassian-labs/chippy/blob/main/LICENSE) file.
+
+[![With ❤️ from Atlassian](https://raw.githubusercontent.com/atlassian-internal/oss-assets/master/banner-cheers.png)](https://www.atlassian.com)

package/bin/chippy.mjs

@@ -0,0 +1,92 @@
+#!/usr/bin/env node
+// Packs a custom Chippy build with extra plugins (see pack.mjs). The agent
+// skill is installed with the skills CLI, not by this package.
+//   npx @atlassian/chippy pack [--config <file>]
+import { readFileSync, realpathSync } from 'node:fs';
+import { dirname, join, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const PACKAGE_ROOT = resolve(dirname(fileURLToPath(import.meta.url)), '..');
+export const SKILL_INSTALL_COMMAND = 'npx skills add atlassian-labs/chippy --skill chippy -g';
+
+const COMMAND_OPTIONS = { pack: ['--config'] };
+const HELP = new Set(['--help', '-h', 'help']);
+const VERSION = new Set(['--version', '-v']);
+
+export function parseArgs(argv) {
+  const args = { command: argv[0], config: 'chippy.config.mjs', help: false, version: false };
+  if (HELP.has(args.command)) return { ...args, command: undefined, help: true };
+  if (VERSION.has(args.command)) return { ...args, command: undefined, version: true };
+  if (args.command === 'install') return args;
+  const allowed = COMMAND_OPTIONS[args.command] ?? [];
+  const value = (i) => {
+    if (i >= argv.length || argv[i].startsWith('-')) throw new Error(`${argv[i - 1]} needs a value`);
+    return argv[i];
+  };
+  for (let i = 1; i < argv.length; i++) {
+    if (HELP.has(argv[i])) args.help = true;
+    else if (VERSION.has(argv[i])) args.version = true;
+    else if (!allowed.includes(argv[i])) throw new Error(`Unknown option for ${args.command}: ${argv[i]}`);
+    else if (argv[i] === '--config') args.config = value(++i);
+  }
+  return args;
+}
+
+function usage(name) {
+  return `Usage: npx ${name} pack [--config <file>]
+       npx ${name} --version
+
+pack     Builds a custom skill and extension with extra plugins from a config
+         file (default chippy.config.mjs). See the package README.
+
+Install the Chippy agent skill with the skills CLI:
+  ${SKILL_INSTALL_COMMAND}
+`;
+}
+
+// The skill used to be installed by this package; point earlier instructions
+// at the skills CLI instead of failing with a bare usage message.
+function installMoved() {
+  return `This package no longer installs the Chippy skill. Install it with the skills CLI:
+  ${SKILL_INSTALL_COMMAND}
+Drop -g to install it in the current project only.
+`;
+}
+
+async function main(argv) {
+  const { name, version } = JSON.parse(readFileSync(join(PACKAGE_ROOT, 'package.json'), 'utf8'));
+  const args = parseArgs(argv);
+  if (args.version) {
+    process.stdout.write(`${version}\n`);
+    return;
+  }
+  if (args.command === 'install') {
+    process.stderr.write(installMoved());
+    process.exitCode = 1;
+    return;
+  }
+  if (args.help || !COMMAND_OPTIONS[args.command]) {
+    process.stdout.write(usage(name));
+    process.exitCode = args.help || args.command === undefined ? 0 : 2;
+    return;
+  }
+  await pack(args.config);
+}
+
+async function pack(configPath) {
+  const { loadPackConfig, packChippy } = await import('./pack.mjs');
+  const result = await packChippy(await loadPackConfig(resolve(configPath)));
+  process.stdout.write(`Packed Chippy:
+  skill      ${result.skillDir}
+  skill zip  ${result.skillZip}
+  extension  ${result.extensionZip}
+`);
+}
+
+// npx and global installs start the bin through a symlink, so compare real paths.
+if (process.argv[1] && realpathSync(process.argv[1]) === realpathSync(fileURLToPath(import.meta.url))) {
+  main(process.argv.slice(2)).catch((error) => {
+    process.stderr.write(`${error.message}\n`);
+    process.exitCode = 1;
+  });
+}