Core
Kompass Workflow infrastructure for AI coding agents
Navigate your way.
Manual steering, steered autonomy, or full autonomy. Kompass keeps AI coding agents on course with token-efficient, composable workflows.
How to install
{
"$schema": "https://opencode.ai/config.json",
"plugins": ["@kompassdev/opencode"]
}Add Kompass to your OpenCode config and restart the app.
Planned
Claude adapter is on the roadmap.
$ /ask is this project cool?
Worker — Answer questions about the current project or code
0 toolcalls
Thinking
Need just enough repository context to answer the question directly.
▸ Explored 2 reads, 1 search
→ read README.md
→ read packages/core/README.md
It has a clear point of view around structured AI workflows.
The shared-core plus adapter split is thoughtful and consistent.
Yes - it is a pretty cool project.
It has a clear point of view around structured AI workflows.
The shared-core plus adapter split is thoughtful and consistent.
Yes - it is a pretty cool project.
$ /branch docs cleanup
Worker — Create a categorized branch from current work
0 toolcalls
Thinking
Summarize uncommitted work, check whether the current branch already looks like a work branch, then generate a short categorized name.
▸ Explored 2 reads, 1 search
→ changes_load uncommitted: true
→ bash git checkout -b docs/reference-cleanup
Created branch: docs/reference-cleanup
From: main
Created branch: docs/reference-cleanup
From: main
$ /commit tighten command docs
Worker — Create a commit from uncommitted work
0 toolcalls
Thinking
Load uncommitted changes, stop if there is nothing to commit, then stage the work and write a conventional message.
▸ Explored 3 reads, 1 search
→ changes_load uncommitted: true
→ bash git add -A
→ bash git commit
Created commit `a1b2c3d`:
docs: tighten command reference pages
Created commit `a1b2c3d`:
docs: tighten command reference pages
$ /commit-and-push
Worker — Create a commit and push it
0 toolcalls
Thinking
Create the commit from current uncommitted work, then push and fall back to upstream setup if needed.
▸ Explored 3 reads, 1 search
→ changes_load uncommitted: true
→ bash git commit
→ bash git push
Created commit `d4e5f6g`:
Pushed to origin/docs/reference-cleanup
Created commit `d4e5f6g`:
Pushed to origin/docs/reference-cleanup
$ /learn docs
Worker — Document non-obvious session learnings
0 toolcalls
Thinking
Review the session for durable, non-obvious learnings and place them in the narrowest useful AGENTS.md scope.
▸ Explored 2 reads, 1 search
→ read AGENTS.md
→ apply_patch update scoped AGENTS guidance
Documented learnings for docs
Files updated: - AGENTS.md: 2 learnings
Documented learnings for docs
Files updated: - AGENTS.md: 2 learnings
$ /skill/create add a release-notes skill
Worker — Create a new skill from project context
0 toolcalls
Thinking
Inspect existing skill conventions, narrow the scope to one reusable workflow, then author the smallest useful skill file set.
▸ Explored 4 reads, 1 search
→ glob .agents/skills/**/SKILL.md
→ read related docs and examples
→ apply_patch create .agents/skills/release-notes/SKILL.md
→ read re-check structure and references
Created skill: release-notes
Path: .agents/skills/release-notes/SKILL.md
Validation: structure and references checked
Created skill: release-notes
Path: .agents/skills/release-notes/SKILL.md
Validation: structure and references checked
$ /skill/optimize .agents/skills/frontend-skill trigger coverage
Worker — Improve an existing skill from grounded feedback
0 toolcalls
Thinking
Load the target skill, identify the weakest parts of the trigger or instructions, then make the smallest improvements that improve activation or output quality.
▸ Explored 4 reads, 1 search
→ read .agents/skills/frontend-skill/SKILL.md
→ read related examples and support files
→ apply_patch tighten description and core guidance
→ read re-check skill files and references
Optimized skill: .agents/skills/frontend-skill
Updated files: SKILL.md
Validation: structure and references checked
Optimized skill: .agents/skills/frontend-skill
Updated files: SKILL.md
Validation: structure and references checked
$ /merge origin/main
Worker — Merge another branch into the current branch
0 toolcalls
Thinking
Confirm the working tree is clean, resolve the merge source, run the merge, and only continue if conflicts can be resolved confidently.
▸ Explored 2 reads, 1 search
→ bash git status --short
→ bash git merge origin/main
Merged origin/main into docs/reference-cleanup
Commit: `9f8e7d6`
Merged origin/main into docs/reference-cleanup
Commit: `9f8e7d6`
$ /rmslop main
Worker — Clean AI-style slop from branch changes
0 toolcalls
Thinking
Load the branch diff, identify noisy or inconsistent AI-shaped edits, clean them up, validate, and commit the cleanup.
▸ Explored 3 reads, 1 search
→ changes_load base: main
→ apply_patch clean awkward comments and style drift
→ bash run validation and commit cleanup
Cleaned branch changes for main...HEAD
Results: Files updated, validation, and commit recorded
Cleaned branch changes for main...HEAD
Results: Files updated, validation, and commit recorded
$ /ticket/ask #42 how do I test this?
Worker — Answer a ticket question and post the reply
0 toolcalls
Thinking
Load the ticket discussion, answer the question from ticket and repo context, then post that answer back to the same ticket.
▸ Explored 3 reads, 1 search
→ ticket_load #42 with comments
→ read relevant test docs
→ ticket_sync post ticket comment
Answered ticket: https://github.com/kompassdev/kompass/issues/42
Answered ticket: https://github.com/kompassdev/kompass/issues/42
$ /ticket/create
Worker — Create a ticket from current change comparison
0 toolcalls
Thinking
Summarize the current change comparison into a short title, description, and checklist structure.
▸ Explored 2 reads, 1 search
→ changes_load main...HEAD
→ ticket_sync title, description, checklists, assignees
Created ticket: Refresh command reference docs
Assigned to @me
Implementation and Validation sections added
Created ticket: Refresh command reference docs
Assigned to @me
Implementation and Validation sections added
$ /ticket/dev #42
Navigator — Implement a ticket through PR creation
0 toolcalls
Thinking
Load the ticket, then orchestrate implementation, branch creation, commit-and-push, and PR creation in order.
▸ Delegated 5 delegations
→ ticket_load #42
worker · dev
worker · branch
worker · commit-and-push
worker · pr/create
Implemented ticket: refresh command docs
PR: https://github.com/kompassdev/kompass/pull/51
Implemented ticket: refresh command docs
PR: https://github.com/kompassdev/kompass/pull/51
$ /ticket/plan #42
Planner — Turn a request or ticket into a scoped plan
0 toolcalls
Thinking
Interpret the planning request, inspect only the relevant repo context, then return a scoped plan without syncing ticket state.
▸ Explored 3 reads, 1 search
→ ticket_load #42 with comments
→ grep reference docs
→ read packages/web/src/content/docs/docs/reference/commands/index.mdx
Title: `Refresh command reference docs`
Plan: short description plus Implementation and Validation checklists
Title: `Refresh command reference docs`
Plan: short description plus Implementation and Validation checklists
$ /ticket/plan-and-sync #42
Planner — Plan work and sync it back to the ticket
0 toolcalls
Thinking
Create a grounded plan, then write the title, description, and checklists back into the ticket flow.
▸ Explored 3 reads, 1 search
→ ticket_load #42 with comments
→ read relevant docs files
→ ticket_sync title, description, implementation checklist, validation checklist
Title: `Refresh command reference docs`
URL: https://github.com/kompassdev/kompass/issues/42
Title: `Refresh command reference docs`
URL: https://github.com/kompassdev/kompass/issues/42
$ /pr/create
Worker — Create a structured PR from current branch work
0 toolcalls
Thinking
Load the branch diff, stop on blockers, resolve ticket handling, push if needed, and create the PR with the required body structure.
▸ Explored 5 reads, 1 search
→ changes_load main...HEAD
→ question Provide Ticket
→ ticket_sync auto-create ticket when selected
→ bash git push
→ pr_sync title, body, base, head, assignees
Created PR: Refresh command reference docs
URL: https://github.com/kompassdev/kompass/pull/51
Ticket: https://github.com/kompassdev/kompass/issues/42
Created PR: Refresh command reference docs
URL: https://github.com/kompassdev/kompass/pull/51
Ticket: https://github.com/kompassdev/kompass/issues/42
$ /pr/fix
Worker — Fix review feedback, then push and reply
0 toolcalls
Thinking
Address the feedback, validate the fixes, then in default mode wait for approval before committing, pushing, or replying on the PR.
▸ Explored 5 reads, 1 search
→ pr_load current PR
→ apply_patch implement requested fixes
→ question Review Fixes
→ bash git push
→ pr_sync reply to addressed threads
PR fix complete for #51
Threads resolved: 2
Pushed: yes
PR fix complete for #51
Threads resolved: 2
Pushed: yes
$ /pr/review 51
Reviewer — Review a PR and publish a graded review
0 toolcalls
Thinking
Load the PR, optional linked ticket, prior review context, and diff, then publish only new eligible findings.
▸ Explored 4 reads, 1 search
→ pr_load PR #51
→ ticket_load linked ticket when one clear ticket exists
→ changes_load base/head refs
→ pr_sync submit graded review
Review submitted for PR #51
Grade: ★★★★☆
Review submitted for PR #51
Grade: ★★★★☆
$ /review main
Reviewer — Review branch changes locally
0 toolcalls
Thinking
Load the diff, inspect the changed files with repo context, and return a local findings summary without publishing comments.
▸ Explored 2 reads, 1 search
→ changes_load base: main
→ read changed files
Review complete for docs/reference-cleanup -> main
Grade: ★★★★☆
Findings: 2 total (0 critical, 1 high, 1 medium, 0 low)
Review complete for docs/reference-cleanup -> main
Grade: ★★★★☆
Findings: 2 total (0 critical, 1 high, 1 medium, 0 low)
$ /dev update the command docs
Navigator — Implement a request and prepare a PR handoff
0 toolcalls
Thinking
Implement the request, validate the result, and stop once the branch is ready for PR creation.
▸ Explored 3 reads, 1 search
→ read relevant docs files
→ apply_patch update docs and demo copy
→ bash run targeted validation
Implementation ready: refresh command docs
Validation: docs checks passed
Ready for PR creation on docs/reference-cleanup
Implementation ready: refresh command docs
Validation: docs checks passed
Ready for PR creation on docs/reference-cleanup
$ /ship
Navigator — Ship current work through delegated steps
0 toolcalls
Thinking
Ensure a work branch, delegate commit creation, then delegate PR creation and stop on blockers.
▸ Delegated 3 delegations
worker · branch
worker · commit
worker · pr/create
Ship flow complete
Branch: Created branch: docs/reference-cleanup
PR: Created PR: Refresh command reference docs
Ship flow complete
Branch: Created branch: docs/reference-cleanup
PR: Created PR: Refresh command reference docs
$ /todo @TODO.md
Navigator — Work through a todo file one item at a time
0 toolcalls
Thinking
Take the first unchecked item only, plan it, get approval, implement it, commit it, mark it complete, and loop.
▸ Delegated 5 delegations
→ read @TODO.md
planner · ticket/plan
→ question Plan Review
worker · dev
worker · commit
Todo complete: @TODO.md
Remaining: 0
Todo complete: @TODO.md
Remaining: 0
Adapters
OpenCode today, more surfaces next
Integrations