point repo references at only-cli/only-cli

The GitHub repo is renamed from oc to only-cli so the repo, the npm
package, and the skills.sh install path all share one name.

.github/workflows/publish.yml

@@ -1,6 +1,6 @@
 # Publishes to npm via OIDC trusted publishing: no token, no OTP prompt.
 # One-time setup on npmjs.com after the package exists: package settings,
-# Trusted Publisher, GitHub Actions, repository only-cli/oc, workflow
+# Trusted Publisher, GitHub Actions, repository only-cli/only-cli, workflow
 # file publish.yml. From then on, publishing a GitHub release ships to npm.
 name: publish
 

CONTRIBUTING.md

@@ -5,8 +5,8 @@ Thanks for wanting to help. This is a small project with strong opinions, so thi
 ## Setup
 
 ```
-git clone https://github.com/only-cli/oc
-cd oc
+git clone https://github.com/only-cli/only-cli
+cd only-cli
 npm install
 npm test
 ```
@@ -41,7 +41,7 @@ Open an issue with the exact command, the output you got, and the output you exp
 
 ## Releasing (maintainer)
 
-Publishing a GitHub release runs `.github/workflows/publish.yml`, which tests and publishes to npm through OIDC trusted publishing: no npm token stored anywhere, no one-time password, and npm attaches provenance automatically. The trusted publisher link (npm package settings, GitHub Actions, repo `only-cli/oc`, workflow `publish.yml`) has to be configured once on npmjs.com after the first manual publish, since npm only lets you attach a trusted publisher to a package that already exists.
+Publishing a GitHub release runs `.github/workflows/publish.yml`, which tests and publishes to npm through OIDC trusted publishing: no npm token stored anywhere, no one-time password, and npm attaches provenance automatically. The trusted publisher link (npm package settings, GitHub Actions, repo `only-cli/only-cli`, workflow `publish.yml`) has to be configured once on npmjs.com after the first manual publish, since npm only lets you attach a trusted publisher to a package that already exists.
 
 ## Maintainer
 

README.md

@@ -34,7 +34,7 @@ The fastest setup is one line in your agent's instructions file (CLAUDE.md, AGEN
 Claude Code users can install the skill instead: copy `skills/only-cli/` into your project's `.claude/skills/` directory (or `~/.claude/skills/` to enable it everywhere). A skill costs almost no tokens until the agent actually invokes it, which fits how this whole project thinks. The same skill also installs through the [skills.sh](https://skills.sh) directory into Claude Code, Cursor, Codex, Copilot, and others:
 
 ```
-npx skills add only-cli/oc
+npx skills add only-cli/only-cli
 ```
 
 No setup at all also works: `npx only-cli` runs without a global install, and the tool teaches its own command surface through `--help`, the `actions:` line at the bottom of every render, and error messages that name the next command to run.

package.json

@@ -28,11 +28,11 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/only-cli/oc.git"
+    "url": "git+https://github.com/only-cli/only-cli.git"
   },
-  "homepage": "https://github.com/only-cli/oc#readme",
+  "homepage": "https://github.com/only-cli/only-cli#readme",
   "bugs": {
-    "url": "https://github.com/only-cli/oc/issues"
+    "url": "https://github.com/only-cli/only-cli/issues"
   },
   "dependencies": {
     "linkedom": "^0.18.12",