@sacho/sacho-aarch64-unknown-linux-musl 0.1.0-dev.11 → 0.1.0-dev.13

package/README.md

@@ -55,6 +55,41 @@ Without mise, npm, or Cargo, download the archive for your platform from
 [GitHub Releases]: https://github.com/dahlia/sacho/releases
 
 
+Agent Skill
+-----------
+
+Sacho ships an [Agent Skill] that teaches AI coding agents, such as Claude Code,
+how to adopt and operate Sacho: writing fragments for users, cutting releases,
+and forward-porting fixes across maintenance branches.
+
+In Claude Code, install it as a plugin. Add this repository as a plugin
+marketplace, then install the `sacho` plugin:
+
+~~~~ text
+/plugin marketplace add dahlia/sacho
+/plugin install sacho@sacho
+~~~~
+
+For other agents, or to install the skill without the plugin system, use the
+[`skills`] CLI, which reads the skill straight from this repository:
+
+~~~~ sh
+npx skills add dahlia/sacho
+~~~~
+
+Add `-a claude-code` to target one agent, `-g` to install it globally, and
+`--skill sacho` to select the skill by name.
+
+The skill is also bundled inside the `@sacho/sacho` npm package, following the
+[`skills-npm`] layout. In a project that depends on that package, run
+`npx skills-npm setup` once to link bundled skills from *node\_modules* into
+your agent on every install.
+
+[Agent Skill]: https://agentskills.io/
+[`skills`]: https://github.com/vercel-labs/skills
+[`skills-npm`]: https://github.com/antfu/skills-npm
+
+
 Documentation
 -------------
 
@@ -138,15 +173,27 @@ staged Git changes or `sacho check --base <revision>` in CI.
 
 When the version is ready, compile and consume its fragments. This command
 releases the version stored by `sacho next`, uses the current local date, and
-starts the next version:
+closes the materialized unreleased region:
 
 ~~~~ sh
-sacho release --next 1.3.0
+sacho release
 ~~~~
 
 If no next version has been set, pass the release version explicitly, for
 example `sacho release 1.2.0`. Use `--date YYYY-MM-DD` when the release date
-must be supplied rather than taken from the local clock.
+must be supplied rather than taken from the local clock. A repository with no
+released changelog sections can cut its first release without fragments. Later
+empty releases require an explicit `--allow-empty`.
+
+Commit and tag that released-only state. When development resumes, start the
+next cycle separately:
+
+~~~~ sh
+sacho next 1.3.0
+~~~~
+
+Pass `--next 1.3.0` to `sacho release` only when the release commit should also
+open the next cycle and retain its empty materialized region.
 
 After committing a release, print its frozen Markdown section with `show`:
 
@@ -225,3 +272,13 @@ is the same insistence this tool makes against generating changelogs from
 commit messages after the fact.
 
 [1]: https://en.wikipedia.org/wiki/Veritable_Records_of_the_Joseon_Dynasty#Compilation_process
+
+
+License
+-------
+
+Copyright (C) 2026 Hong Minhee.
+
+Sacho is free software licensed under the GNU General Public License version 3
+only. It comes with no warranty, to the extent permitted by law. See
+[*LICENSE*](./LICENSE) for the full terms.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sacho/sacho-aarch64-unknown-linux-musl",
-  "version": "0.1.0-dev.11+f8249e8",
+  "version": "0.1.0-dev.13+e6331b9",
   "description": "The Sacho binary for aarch64-unknown-linux-musl",
   "license": "GPL-3.0-only",
   "author": "Hong Minhee <hong@minhee.org>",