Skip to content

Command cheat sheet

This page lists every command you type to use Kiyo and the order to run them in. Kiyo has no CLI of its own. You use two install commands from your host, then eight Skill selectors, one per Skill. After you select a Skill, you describe the task in plain language.

How many commands?

Section titled “How many commands?”
Group Count When Commands
Install 2 Once per machine Add the catalog, then install the package
Onboard 1 (Init) Once per repository init in two passes: preview, then initialize
Daily work 6 Per task, as needed requirement, architecture, implement, test, review, security
Keep context current 1 (Memory) After changes, or when context looks stale memory
Total 10 2 install + 8 Skills

git status is not a Kiyo command, but use it after every read-only step to confirm nothing changed.

The order to run them

Section titled “The order to run them”

  1. Install the package (once per machine). Run the two commands for your host.

    Claude Code session
    /plugin marketplace add 0xPratyaDev7x/kiyo-axiom-framework
    /plugin install kiyo-axiom-framework@kiyo-codejadee

    Then: open your host’s Skill list and check that all eight Skills are visible. This catalog route is a development route with no recorded host test (NOT_TESTED). See Installation.

  2. Preview onboarding (once per repository). Select Init and send:

    /kiyo-axiom-framework:init
    Preview onboarding for this repository; report evidence, unknowns and proposed Memory/config/bootstrap changes without writing files.

    Then: read the report and run git status. Preview must change zero files.

  3. Initialize the approved state. If the proposal looks right, select Init again and send:

    /kiyo-axiom-framework:init
    Create only the proposed project-local Memory/config; preserve existing instructions.

    Then: review the new .kiyo/ files (typically .kiyo/policy.md and .kiyo/memory/index.md) and commit them yourself if you want to keep them.

  4. Work task by task. Pick the Skills that fit the task. Each Skill stops when it is done and never starts the next one, so you select each step yourself.

Daily Skills, in a typical order

Section titled “Daily Skills, in a typical order”

A typical feature or fix moves from defining the work to verifying it. Skip the steps you do not need. The selectors below use the Claude Code and Copilot VS Code form. For Codex (CLI and VS Code) and Copilot CLI, pick the same Skill from the host’s Skill picker.

# Skill Selector Do this Example request Writes files?
1 Requirement /kiyo-axiom-framework:requirement Turn a raw request into a requirement with a readiness verdict “Draft requirements for Excel export using repository evidence. Identify unresolved fields and permissions; do not implement.” No (chat), unless you name a specification path
2 Architecture /kiyo-axiom-framework:architecture Check impact or drift before a change that crosses a module boundary “Compare ADR-007 with this module; report deviations only.” No
3 Implement /kiyo-axiom-framework:implement Make the scoped change and run the checks that apply “Fix the supplied boundary error and add its regression test; preserve unrelated edits.” Yes: authorized code, tests, and docs
4 Test /kiyo-axiom-framework:test assess gaps, run existing checks, or write tests “Assess authorization test gaps in this module; no writes or execution.” Only in write mode
5 Review /kiyo-axiom-framework:review Review the diff before you commit “Review my unstaged changes; do not edit or run project scripts.” No
6 Security /kiyo-axiom-framework:security Assess sensitive code, a third-party Skill, or policy “Review this supplied Skill package against AST01–AST10 without executing it.” No
7 Memory /kiyo-axiom-framework:memory check Memory against the branch, then sync if something changed “Compare these observations and decisions with this branch.” Only in sync or repair mode

Select the Skill, then send the request as ordinary text. The examples are illustrative; replace the feature, module, or decision names with your own.

Modes are words, not extra commands

Section titled “Modes are words, not extra commands”

Some Skills have modes. You choose a mode with words in your request, not with a flag or a separate command.

Skill Modes Read-only modes
Init preview, initialize preview
Test assess, run, write assess
Security application, skills, governance, self-check all
Memory show, check, sync, repair show, check

Commands to avoid

Section titled “Commands to avoid”
  • A host’s built-in /init or /review. These are different commands from Kiyo’s Init and Review.
  • Guessed aliases such as /kiyo-init or $kiyo.init.
Section titled “Related”