kortix-system

Document Kortix project configuration, CLI operations, and change management workflows.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/MuhammadUA/Axe --skill kortix-system-muhammadua
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kortix-system
Source: https://github.com/MuhammadUA/Axe/tree/main/.kortix/opencode/skills/kortix-system
Command: npx skills add https://github.com/MuhammadUA/Axe --skill kortix-system-muhammadua

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the frustration of scattered, outdated, or incomplete documentation for Kortix projects, giving you a single authoritative source for all platform configuration, CLI operations, and workflow rules.

Core Features & Use Cases

  • Strict Config Boundary Reference: Clarifies the exact split between Kortix-owned config (kortix.toml, .kortix/) and OpenCode-owned config (.kortix/opencode/), so you never misplace project settings.
  • Full CLI & CR Workflow Guidance: Covers every kortix CLI command, flag, and token rule, plus the mandatory change request (CR) process for landing session work on main, so you can manage projects, secrets, sessions, and deployments from the terminal or agent.
  • Complete OpenCode Runtime Reference: Includes official docs for agents, skills, slash commands, custom tools, plugins, MCP servers, permissions, AGENTS.md rules, and model configuration, so you can customize the agent runtime to fit your workflow.
  • Use Case: Use this skill when setting up a new Kortix project, debugging a failed session or trigger, opening a change request to merge code to main, or configuring custom OpenCode agents and tools for your team.

Quick Start

Use the kortix-system skill to get immediate, accurate answers for any question about Kortix project configuration, kortix CLI usage, change request workflows, or OpenCode runtime customization.

Frequently Asked Questions about kortix-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit kortix.toml and manage Kortix project configuration?

Kortix project configuration is managed by editing the kortix.toml manifest file. A strict platform-config boundary separates Kortix-owned settings in kortix.toml and .kortix/ from OpenCode-owned config in .kortix/opencode/.

What is the change request lifecycle for merging session work to main in Kortix?

The Kortix change request (CR) lifecycle is the mandatory process for landing session work on main. It involves creating a change request from a session sandbox and merging it back to the main branch using specific kortix CLI commands.

How do I configure custom OpenCode agents, tools, and MCP servers?

OpenCode runtime customization is configured within the .kortix/opencode/ directory. This includes setting up custom agents, skills, slash commands, plugins, MCP servers, permissions, AGENTS.md rules, and model configuration.

Why is my Kortix session or trigger failing?

Failed Kortix sessions or triggers can be debugged by verifying the strict config boundary between kortix.toml and OpenCode-owned settings. Check CLI command flags, project-scoped token rules, and session sandbox management state.

Does the kortix CLI support project-scoped tokens for secrets and deployments?

Yes, the kortix CLI uses a project-scoped token model to manage secrets, sessions, and deployments. It provides a full command set with specific flags and token rules for terminal or agent-based project management.

When should I not use Kortix session sandboxes for code changes?

You should not bypass Kortix session sandboxes when making code changes intended for main. The platform enforces a mandatory change request process, meaning direct commits to main without a CR are not supported.