@laitszkin/apollo-toolkit 3.14.6 → 3.14.7

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to this repository are documented in this file.
 
+## [v3.14.7] - 2026-05-16
+
+### Changed
+
+- Rename `archive-specs` to `archive` for consistency with other short skill aliases.
+
 ## [v3.14.6] - 2026-05-16
 
 ### Changed

package/README.md

@@ -7,7 +7,7 @@ A curated skill catalog for Codex, OpenClaw, Trae, Agents, and Claude Code with
 - docs-project
 - analyse-app-logs
 - answering-questions-with-research
-- archive-specs
+- archive
 - cjk-pdf
 - codex-memory-manager
 - commit

package/{archive-specs → archive}/README.md

@@ -1,4 +1,4 @@
-# archive-specs
+# archive
 
 A documentation skill that converts completed spec files and batch-level coordination files into the standardized project documentation structure and archives the consumed planning files. It delegates documentation generation to `docs-project` and constraint file refresh to `maintain-project-constraints`.
 

package/{archive-specs → archive}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: archive-specs
+name: archive
 description: 將已完成的spec歸檔到 `docs/archive/` 下。當你需要將spec歸檔時，調用這個技能。
 ---
 

package/archive/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "archive"
+  short_description: "Convert completed specs into standardized project docs and archive the consumed plans"
+  default_prompt: "Use $archive to inventory the project's spec.md/tasks.md/checklist.md/contract.md/design.md files plus any batch-level coordination.md, reconcile them with the current repository, use coordination.md to understand shared preparation and legacy-replacement direction across parallel plan sets, delegate documentation generation to docs-project which produces standardized docs under docs/features/ (BDD user-facing features), docs/architecture/ (macro-level design principles), and docs/principles/ (code conventions and constraints), then delegate AGENTS.md/CLAUDE.md refresh to maintain-project-constraints which writes business goals, common commands, and the project documentation index. Archive the consumed source plans after successful conversion, deleting them only when the repository clearly does not need historical retention and keeping coordination.md active while any spec set still depends on it."

package/commit/README.md

@@ -8,7 +8,7 @@ A Codex skill for commit workflows without release/version operations.
 
 1. Inspecting git status and staged state.
 2. Running `review-change-set` as a blocking gate whenever the change set includes code changes.
-3. Running `archive-specs` during submission to convert completed spec sets and archive them, or when existing project docs need normalization.
+3. Running `archive` during submission to convert completed spec sets and archive them, or when existing project docs need normalization.
 4. Keeping root `CHANGELOG.md` `Unreleased` aligned with the actual pending change set, including removing stale conflicting bullets when needed.
 5. Running `docs-project` and `maintain-project-constraints` before commit.
 6. Running additional dependency skills for code-affecting diffs when their coverage is needed.
@@ -23,7 +23,7 @@ Use this skill when the user asks to commit/push/submit changes and does **not**
 - tagging
 - release changelog workflows
 
-If the repository contains a completed spec set, convert it into the categorized `archive-specs` project-doc structure during submission and archive the consumed plan files. Treat `spec.md`, `tasks.md`, and `checklist.md` semantically: unchecked task or decision checkboxes do not automatically mean the work is unfinished when the docs clearly show they were not selected, replaced, deferred, or marked `N/A`.
+If the repository contains a completed spec set, convert it into the categorized `archive` project-doc structure during submission and archive the consumed plan files. Treat `spec.md`, `tasks.md`, and `checklist.md` semantically: unchecked task or decision checkboxes do not automatically mean the work is unfinished when the docs clearly show they were not selected, replaced, deferred, or marked `N/A`.
 
 Treat root `CHANGELOG.md` `Unreleased` as the source of pending release notes: add or refresh only the bullets that match the current change, keep unrelated pending bullets, and remove older conflicting bullets when the new implementation supersedes them.
 

package/commit/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Commit and Push"
   short_description: "Submit local changes with commit and push only"
-  default_prompt: "Use $commit to inspect the current git state and classify the diff. Treat every conditional gate whose scenario is met as blocking before any commit: if the change set includes code changes, run $review-change-set; if completed specs should be converted or docs need normalization, ensure $archive-specs runs through $submission-readiness-check; if changelog synchronization is needed, complete it before continuing. Then run any additional required code-quality skills, hand the repository to $submission-readiness-check so it can synchronize completed plan archives, project docs, AGENTS.md/CLAUDE.md, and CHANGELOG.md before any commit, confirm root CHANGELOG.md Unreleased reflects the actual pending change set, preserve user staging intent, create a concise Conventional Commit, and push to the intended branch without any versioning or release steps."
+  default_prompt: "Use $commit to inspect the current git state and classify the diff. Treat every conditional gate whose scenario is met as blocking before any commit: if the change set includes code changes, run $review-change-set; if completed specs should be converted or docs need normalization, ensure $archive runs through $submission-readiness-check; if changelog synchronization is needed, complete it before continuing. Then run any additional required code-quality skills, hand the repository to $submission-readiness-check so it can synchronize completed plan archives, project docs, AGENTS.md/CLAUDE.md, and CHANGELOG.md before any commit, confirm root CHANGELOG.md Unreleased reflects the actual pending change set, preserve user staging intent, create a concise Conventional Commit, and push to the intended branch without any versioning or release steps."

package/merge-changes-from-local-branches/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Merge Changes from Local Branches"
   short_description: "Merge named local branches back into the current branch with checked conflict resolution"
-  default_prompt: "Use $merge-changes-from-local-branches to inventory the current branch plus the named local branches that should be merged, inspect active batch-spec `coordination.md` files under `docs/plans/` and follow their documented merge order when present, match the merge scope by branch name instead of branch ancestry, merge only those in-scope branches back into the same current branch, resolve conflicts by reading and composing the correct behavior instead of relying on blanket merge strategies, run targeted verification after conflictful merges, delete successfully merged source branches and detached worktrees only after verification succeeds, then run $commit for submission-readiness and the final local commit on that branch without pushing unless the user explicitly requested remote update in the same thread. Do not invoke $archive-specs from this skill."
+  default_prompt: "Use $merge-changes-from-local-branches to inventory the current branch plus the named local branches that should be merged, inspect active batch-spec `coordination.md` files under `docs/plans/` and follow their documented merge order when present, match the merge scope by branch name instead of branch ancestry, merge only those in-scope branches back into the same current branch, resolve conflicts by reading and composing the correct behavior instead of relying on blanket merge strategies, run targeted verification after conflictful merges, delete successfully merged source branches and detached worktrees only after verification succeeds, then run $commit for submission-readiness and the final local commit on that branch without pushing unless the user explicitly requested remote update in the same thread. Do not invoke $archive from this skill."

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@laitszkin/apollo-toolkit",
-  "version": "3.14.6",
+  "version": "3.14.7",
   "description": "Apollo Toolkit npm installer for managed skill copying across Codex, OpenClaw, and Trae.",
   "license": "MIT",
   "author": "LaiTszKin",

package/version-release/README.md

@@ -9,7 +9,7 @@ A Codex skill for explicit release workflows: code/documentation alignment, vers
 1. Inspect the current repository state and the curated `CHANGELOG.md` `Unreleased` content.
 2. Run `review-change-set` as a blocking gate whenever the release includes code changes.
 3. Run additional quality gates for code-affecting changes when their coverage is needed.
-4. Run `archive-specs` before finalizing the release to convert completed spec sets and archive them, or when existing project docs need normalization.
+4. Run `archive` before finalizing the release to convert completed spec sets and archive them, or when existing project docs need normalization.
 5. Align project code and categorized project docs.
 6. Resolve version and tag details by reading the current version and existing tag/release state first.
 7. Update version files and cut the release directly from `CHANGELOG.md` `Unreleased`.
@@ -26,7 +26,7 @@ Use this skill only when the user explicitly asks for:
 - tag creation/publishing
 - GitHub release publication
 
-If the repository contains a completed spec set, convert it into the categorized `archive-specs` project-doc structure before finalizing the release and archive the consumed plan files. Treat `spec.md`, `tasks.md`, and `checklist.md` semantically: unchecked task or decision checkboxes do not automatically mean the work is unfinished when the docs clearly show they were not selected, replaced, deferred, or marked `N/A`.
+If the repository contains a completed spec set, convert it into the categorized `archive` project-doc structure before finalizing the release and archive the consumed plan files. Treat `spec.md`, `tasks.md`, and `checklist.md` semantically: unchecked task or decision checkboxes do not automatically mean the work is unfinished when the docs clearly show they were not selected, replaced, deferred, or marked `N/A`.
 
 Do not rebuild release notes from `git diff`. Publish from the already curated root `CHANGELOG.md` `Unreleased` content by moving it into the target version entry and clearing `Unreleased` afterward.
 

package/archive-specs/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "archive-specs"
-  short_description: "Convert completed specs into standardized project docs and archive the consumed plans"
-  default_prompt: "Use $archive-specs to inventory the project's spec.md/tasks.md/checklist.md/contract.md/design.md files plus any batch-level coordination.md, reconcile them with the current repository, use coordination.md to understand shared preparation and legacy-replacement direction across parallel plan sets, delegate documentation generation to docs-project which produces standardized docs under docs/features/ (BDD user-facing features), docs/architecture/ (macro-level design principles), and docs/principles/ (code conventions and constraints), then delegate AGENTS.md/CLAUDE.md refresh to maintain-project-constraints which writes business goals, common commands, and the project documentation index. Archive the consumed source plans after successful conversion, deleting them only when the repository clearly does not need historical retention and keeping coordination.md active while any spec set still depends on it."