fix: publishing not working

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets).
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md).

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.3/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": ["@diffity/git", "@diffity/parser", "@diffity/ui"]
+}

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "diffity",
+  "name": "@diffity",
   "version": "0.1.0",
   "private": true,
   "type": "module",
@@ -15,7 +15,10 @@
     "build:skills": "tsx scripts/build-skills.ts",
     "test": "npm run test -w @diffity/parser && npm run test -w @diffity/ui",
     "link-dev": "tsx scripts/link-dev.ts",
-    "dev": "tsx scripts/dev.ts"
+    "dev": "tsx scripts/dev.ts",
+    "changeset": "changeset",
+    "version": "changeset version",
+    "release": "npm run build && changeset publish"
   },
   "keywords": [
     "git",
@@ -26,6 +29,7 @@
   "author": "",
   "license": "PolyForm-Shield-1.0.0",
   "devDependencies": {
+    "@changesets/cli": "^2.30.0",
     "concurrently": "^9.2.1",
     "gray-matter": "^4.0.3",
     "tsx": "^4.21.0"

packages/cli/CHANGELOG.md

@@ -0,0 +1,7 @@
+# diffity
+
+## 0.1.1
+
+### Patch Changes
+
+- initial release

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "diffity",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "GitHub-style git diff viewer in the browser",
   "type": "module",
   "bin": {

packages/git/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@diffity/git",
   "version": "0.1.0",
+  "private": true,
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

packages/parser/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@diffity/parser",
   "version": "0.1.0",
+  "private": true,
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

skills/diffity-resolve/SKILL.md

@@ -44,19 +44,12 @@ diffity agent reply <id> --body "<text>"
 2. If there are no open threads, tell the user there's nothing to resolve.
 3. For each open thread:
    a. **Skip** general comments (filePath `__general__`) — these are summaries, not actionable code changes.
-   b. **Skip** threads explicitly tagged with the literal text `[question]` or `[nit]` in the comment body — these don't require code changes. Tell the user you skipped them and why.
-      - **Important**: Do NOT skip comments just because they are phrased as questions. Many review comments use questions to request changes or ask the agent to analyze the code (e.g. "missing something here?", "should this be X instead?", "is this handling Y correctly?"). These require you to read the code, analyze, and either make a fix or reply with your findings.
-   c. Read the comment body from the JSON output and understand what is being asked.
-   d. Read the relevant source file to understand the full context around the commented lines.
-   e. Decide the appropriate action:
-      - If the comment requests a specific code change → make the change using the Edit tool, then resolve the thread:
-        ```
-        diffity agent resolve <thread-id> --summary "Fixed: <brief description of what was changed>"
-        ```
-      - If the comment asks you to review/analyze the code (e.g. "missing something?", "is this right?") → analyze the code thoroughly, then reply with your findings:
-        ```
-        diffity agent reply <thread-id> --body "<your analysis>"
-        ```
-        If your analysis reveals a problem, also fix it and resolve the thread. If the code looks correct, reply explaining why it's fine.
+   b. **Skip** threads tagged `[question]` or `[nit]` — these don't require code changes. Tell the user you skipped them and why.
+   c. Read the comment body from the JSON output and understand what change is requested.
+   d. Read the relevant source file to understand the full context around the commented lines, then make the requested code change using the Edit tool.
+   e. After making the change, resolve the thread with a summary:
+      ```
+      diffity agent resolve <thread-id> --summary "Fixed: <brief description of what was changed>"
+      ```
 4. After resolving all applicable threads, run `diffity agent list` to confirm status.
 5. Tell the user to check the browser — resolved status will appear within 2 seconds via polling.