@laitszkin/apollo-toolkit 2.12.4 → 2.12.5

package/AGENTS.md

@@ -58,6 +58,16 @@ This repository enables users to install and run a curated set of reusable agent
 - Users can prepare and publish versioned releases with changelog and tag workflows.
 - Users can generate long-form videos by orchestrating storyboard, voice, and Remotion-based production steps.
 
+## Common Commands
+
+- `npm test` - 執行 Node 測試套件。
+- `node bin/apollo-toolkit.js` - 直接從倉庫啟動 Apollo Toolkit CLI。
+- `node bin/apollo-toolkit.js codex openclaw trae` - 以非互動方式將技能安裝到指定目標。
+- `python3 scripts/validate_skill_frontmatter.py` - 驗證所有頂層技能 `SKILL.md` 的 frontmatter。
+- `python3 scripts/validate_openai_agent_config.py` - 驗證所有技能 `agents/openai.yaml` 設定。
+- `./scripts/install_skills.sh codex` - 用本地安裝腳本把技能安裝到 Codex 目錄。
+- `./scripts/install_skills.sh all` - 用本地安裝腳本同步安裝到所有支援目標。
+
 ## Core Project Purpose
 
 - Provide a curated set of reusable agent skills that can be installed into Codex/OpenClaw/Trae skill directories.

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this repository are documented in this file.
 
 ## [Unreleased]
 
+## [v2.12.5] - 2026-04-01
+
+### Changed
+- Update `maintain-project-constraints` so generated `AGENTS.md` templates must include a factual `Common Commands` section grounded in repository-owned command entry points such as CLIs, package scripts, and task runners.
+- Refresh the Apollo Toolkit root `AGENTS.md` guidance with repository-specific common commands for the local CLI, validation scripts, tests, and install flows.
+
 ## [v2.12.4] - 2026-04-01
 
 ### Added

package/maintain-project-constraints/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: maintain-project-constraints
-description: Automatically create and maintain AGENTS.md so it stays aligned with the current repository architecture, core business flow, project purpose, and coding conventions. Use when AGENTS.md is missing or may be outdated after code changes.
+description: Automatically create and maintain AGENTS.md so it stays aligned with the current repository architecture, core business flow, common commands, project purpose, and coding conventions. Use when AGENTS.md is missing or may be outdated after code changes.
 ---
 
 # Maintain Project Constraints
@@ -17,7 +17,7 @@ description: Automatically create and maintain AGENTS.md so it stays aligned wit
 - Evidence: Infer repository architecture, business flow, and conventions from current code and docs rather than assumptions.
 - Execution: Create or align `AGENTS.md` only after building a concrete inventory of implemented capabilities.
 - Quality: Keep every statement traceable, remove stale guidance, and ensure `Core business flow` stays exhaustive and concrete.
-- Output: Maintain a concise root-level `AGENTS.md` with the required sections and repository-specific wording.
+- Output: Maintain a concise root-level `AGENTS.md` with the required sections, repository-specific wording, and a factual `Common Commands` section when the repository exposes stable command entry points.
 
 ## Goal
 
@@ -38,9 +38,18 @@ After completing any code modification task, proactively run this skill to verif
 
 - Project architecture
 - Core business flow
+- Common commands
 - Core project purpose
 - Code style and coding conventions
 
+For the `Common Commands` section, always use this format:
+
+1. Include only commands that are real, current, and useful in this repository.
+2. Prefer repository-owned entry points such as package scripts, CLIs, `bin/` programs, `scripts/`, `Makefile`, `justfile`, or other documented task runners.
+3. For each command, explain when to use it in one short phrase instead of listing bare commands with no context.
+4. Prioritize commands that help an agent inspect, validate, build, test, or operate repository-specific workflows.
+5. Do not invent commands, aliases, flags, or task names that are not traceable to the repository.
+
 For the `Core business flow` section, always use this format:
 
 1. One short sentence that summarizes what the repository currently enables.
@@ -51,6 +60,13 @@ Example:
 
 ```markdown
 
+## Common Commands
+
+- `npm test` — run the repository's automated test suite.
+- `python3 scripts/validate_skill_frontmatter.py` — validate every top-level `SKILL.md` frontmatter block.
+- `python3 scripts/validate_openai_agent_config.py` — validate every `agents/openai.yaml` interface config.
+- `./scripts/install_skills.sh codex` — install the current toolkit into the local Codex skills directory.
+
 ## Core Business Flow
 
 This project enables users to manage and run reusable automation workflows.
@@ -69,11 +85,13 @@ This project enables users to manage and run reusable automation workflows.
 - Read the repository before writing:
   - root docs (`README`, contribution docs, design docs)
   - key source directories and entry points
+  - repository command surfaces such as `package.json`, `bin/`, `scripts/`, `Makefile`, `justfile`, or equivalent task runners
   - user-facing features such as commands, routes, workflows, tasks, or installable modules
   - representative modules that show coding patterns
   - test directories and tooling/config files
 - Infer architecture and conventions from real code, not assumptions.
 - Build a concrete inventory of all currently implemented capabilities before drafting `Core business flow`.
+- Build a separate inventory of stable, repository-specific commands before drafting `Common Commands`.
 
 ### 2) Create AGENTS.md when missing
 
@@ -81,7 +99,9 @@ When `AGENTS.md` is absent:
 
 - Create a new root-level `AGENTS.md`.
 - Document architecture, business flow, purpose, and coding conventions from observed facts.
+- Document the repository's common commands from observed command entry points and docs.
 - Write `Core business flow` as one summary sentence followed by unordered bullets that cover every current capability found in the repository.
+- Write `Common commands` as short bullets in the style of ``- `command` — when to use it.``.
 - Keep language specific to this repository; avoid generic boilerplate.
 
 ### 3) Align AGENTS.md when drift is detected
@@ -91,12 +111,15 @@ When `AGENTS.md` exists but is outdated:
 - Re-read changed or high-impact modules.
 - Update only sections that no longer match reality.
 - Expand or trim the `Core business flow` bullet list so it still covers all currently implemented capabilities.
+- Expand, trim, or replace the `Common Commands` list whenever command entry points or recommended workflows have changed.
 - Preserve correct existing content and structure where possible.
 
 ### 4) Quality checks before finishing
 
 - Ensure every statement in `AGENTS.md` is traceable to current repository files.
 - Remove stale paths, renamed components, and obsolete workflows.
+- Remove stale commands, flags, or task names that no longer exist.
+- Verify every command in `Common Commands` is either documented in repository docs or directly supported by the current codebase.
 - Verify the `Core business flow` section includes a one-sentence summary plus unordered bullets for all currently existing capabilities; do not leave major functions unlisted.
 - Keep instructions concise, concrete, and operational for future agents.
 
@@ -106,4 +129,5 @@ When `AGENTS.md` exists but is outdated:
 - Prefer repository terms already used in code/docs.
 - Do not include speculative architecture claims.
 - In `Core business flow`, prefer many short bullets over a few vague bullets; when the product grows, add more bullets so the list remains exhaustive.
+- In `Common Commands`, prefer the smallest useful set of high-signal commands over an exhaustive dump of every helper script.
 - Keep the document focused on how agents should understand and operate in this project.

package/maintain-project-constraints/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Maintain Project Constraints"
-  short_description: "Automatically create and maintain AGENTS.md so it stays aligned with the current repository architecture, core business flow, project purpose, and coding conventions. Use when AGENTS.md is missing or may be outdated after code changes."
-  default_prompt: "Use $maintain-project-constraints to automatically create and maintain AGENTS.md so it stays aligned with the current repository architecture, core business flow, project purpose, and coding conventions. Use when AGENTS.md is missing or may be outdated after code changes."
+  short_description: "Automatically create and maintain AGENTS.md so it stays aligned with the current repository architecture, core business flow, common commands, project purpose, and coding conventions. Use when AGENTS.md is missing or may be outdated after code changes."
+  default_prompt: "Use $maintain-project-constraints to automatically create and maintain AGENTS.md so it stays aligned with the current repository architecture, core business flow, common commands, project purpose, and coding conventions. Use when AGENTS.md is missing or may be outdated after code changes."

package/package.json

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