@xenonbyte/xsk 0.1.1 → 0.1.2

package/README.md

@@ -1,5 +1,7 @@
 # xsk
 
+**English** | [简体中文](README.zh-CN.md)
+
 > Curate a small set of agent skills and install them across Claude Code, Codex, opencode, and Gemini, with manifest-backed safety.
 
 [![Node](https://img.shields.io/badge/node-%3E%3D20-3c873a)](https://nodejs.org/)

package/README.zh-CN.md

@@ -1,5 +1,7 @@
 # xsk
 
+[English](README.md) | **简体中文**
+
 > 精选一小组 agent skill，以 manifest 记录作为安全保障，安装到 Claude Code、Codex、opencode 与 Gemini。
 
 [![Node](https://img.shields.io/badge/node-%3E%3D20-3c873a)](https://nodejs.org/)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xenonbyte/xsk",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Agent skill aggregator. Install a curated set of agent skills across Claude Code, Codex, opencode, and Gemini with manifest-backed safety.",
   "license": "MIT",
   "bin": {

package/skills/archive-req/SKILL.md

@@ -24,10 +24,15 @@ Match the intent, not the exact words. Common cues:
 5. Write the fully-updated archived content to `.xsk/requirements/archive/<slug>.md`: set `status: archived`, add `archived_at: <ISO date>`, and preserve every other frontmatter field and the entire body unchanged.
 6. Confirm it landed as written, then remove the source active doc.
 7. After archiving, confirm zero active documents remain.
+8. Offer to commit the archival, git-aware. The archive copy lives under the git-ignored `requirements/archive/`, so from git's view the only change is the deletion of the source active doc. If the project is a git repository and that active doc was tracked (`git ls-files --error-unmatch <path>` succeeds), ask the user once whether to commit this archival, and act on the answer:
+   - On yes, commit only that deleted path. Stage the deletion first, then commit only that path: `git add -- <the removed active doc path> && git commit -m "docs(xsk): archive requirement <slug>" -- <the removed active doc path>`. Never `git add -A` or `git add .`.
+   - On no, leave the working tree as is and report that the deletion was left for the user to commit.
+
+   If the doc was untracked, or the project is not a git repository, skip the prompt and say nothing about committing.
 
 ## Output
 
-Either a one-line refusal that names the missing/invalid slug, a stop-and-ask response when `.xsk/requirements/archive/<slug>.md` already exists and it was left unchanged, writing nothing, or the archived path (`.xsk/requirements/archive/<slug>.md`) plus confirmation that it landed before the source active doc was removed and that no active requirement docs remain.
+Either a one-line refusal that names the missing/invalid slug, a stop-and-ask response when `.xsk/requirements/archive/<slug>.md` already exists and it was left unchanged, writing nothing, or the archived path (`.xsk/requirements/archive/<slug>.md`) plus confirmation that it landed before the source active doc was removed and that no active requirement docs remain, and, when the removed doc was tracked by git, whether the user committed the archival or left it uncommitted.
 
 ## Conventions shared across xsk skills
 

package/skills/write-req/SKILL.md

@@ -53,9 +53,14 @@ created_at: <ISO date>
 ---
 ```
 
+**9. Offer to commit, git-aware.** Only after the doc passes the self-audit and is finalized, decide whether to offer a commit. If the project is not a git repository (`git rev-parse --is-inside-work-tree` fails), or the requirement doc is byte-identical to what git already tracks, skip silently and say nothing about committing. Otherwise ask the user once whether to commit this requirement, and act on the answer:
+
+- On yes, commit only the paths this run wrote: the requirement doc, plus `.xsk/.gitignore` if this run created it. Stage those exact paths first, then commit only them: `git add -- <those paths> && git commit -m "docs(xsk): write requirement <slug>" -- <those paths>`. Stage first because a bare `git commit -- <path>` rejects an untracked new doc. Never `git add -A` or `git add .`, so unrelated working-tree changes are never swept in.
+- On no, leave the doc uncommitted and report that it was left for the user to commit.
+
 ## Output
 
-The path of the requirement file, with confirmation that it is now the single active doc.
+The path of the requirement file, with confirmation that it is now the single active doc, and, when a commit was offered, whether the user committed it or left it uncommitted.
 
 ## Conventions shared across xsk skills
 

package/templates/fragments/archive-req.behavior.md

@@ -5,3 +5,8 @@
 5. Write the fully-updated archived content to `.xsk/requirements/archive/<slug>.md`: set `status: archived`, add `archived_at: <ISO date>`, and preserve every other frontmatter field and the entire body unchanged.
 6. Confirm it landed as written, then remove the source active doc.
 7. After archiving, confirm zero active documents remain.
+8. Offer to commit the archival, git-aware. The archive copy lives under the git-ignored `requirements/archive/`, so from git's view the only change is the deletion of the source active doc. If the project is a git repository and that active doc was tracked (`git ls-files --error-unmatch <path>` succeeds), ask the user once whether to commit this archival, and act on the answer:
+   - On yes, commit only that deleted path. Stage the deletion first, then commit only that path: `git add -- <the removed active doc path> && git commit -m "docs(xsk): archive requirement <slug>" -- <the removed active doc path>`. Never `git add -A` or `git add .`.
+   - On no, leave the working tree as is and report that the deletion was left for the user to commit.
+
+   If the doc was untracked, or the project is not a git repository, skip the prompt and say nothing about committing.

package/templates/fragments/archive-req.output.md

@@ -1 +1 @@
-Either a one-line refusal that names the missing/invalid slug, a stop-and-ask response when `.xsk/requirements/archive/<slug>.md` already exists and it was left unchanged, writing nothing, or the archived path (`.xsk/requirements/archive/<slug>.md`) plus confirmation that it landed before the source active doc was removed and that no active requirement docs remain.
+Either a one-line refusal that names the missing/invalid slug, a stop-and-ask response when `.xsk/requirements/archive/<slug>.md` already exists and it was left unchanged, writing nothing, or the archived path (`.xsk/requirements/archive/<slug>.md`) plus confirmation that it landed before the source active doc was removed and that no active requirement docs remain, and, when the removed doc was tracked by git, whether the user committed the archival or left it uncommitted.

package/templates/fragments/write-req.behavior.md

@@ -33,3 +33,8 @@ slug: <slug>
 created_at: <ISO date>
 ---
 ```
+
+**9. Offer to commit, git-aware.** Only after the doc passes the self-audit and is finalized, decide whether to offer a commit. If the project is not a git repository (`git rev-parse --is-inside-work-tree` fails), or the requirement doc is byte-identical to what git already tracks, skip silently and say nothing about committing. Otherwise ask the user once whether to commit this requirement, and act on the answer:
+
+- On yes, commit only the paths this run wrote: the requirement doc, plus `.xsk/.gitignore` if this run created it. Stage those exact paths first, then commit only them: `git add -- <those paths> && git commit -m "docs(xsk): write requirement <slug>" -- <those paths>`. Stage first because a bare `git commit -- <path>` rejects an untracked new doc. Never `git add -A` or `git add .`, so unrelated working-tree changes are never swept in.
+- On no, leave the doc uncommitted and report that it was left for the user to commit.

package/templates/fragments/write-req.output.md

@@ -1 +1 @@
-The path of the requirement file, with confirmation that it is now the single active doc.
+The path of the requirement file, with confirmation that it is now the single active doc, and, when a commit was offered, whether the user committed it or left it uncommitted.