How are relevant wiki pages chosen?

We list wiki pages using list_wiki_pages with the repo owner and name, then match page titles and descriptions to your question before fetching content with get_wiki_page.

What if the repo has no wiki?

We’ll suggest setting up a wiki in the cubic dashboard to enable future context extraction.

How is the final answer presented?

The skill provides a focused synthesis that cites specific wiki pages and connects the information to the relevant files or modules—avoiding a full dump of wiki content.

codebase-context

npx machina-cli add skill mrge-io/cubic-claude-plugin/codebase-context --openclaw

Files (1)

SKILL.md

1.4 KB

Codebase Context from Wiki

This skill queries cubic's AI-generated wiki to provide architectural context about the codebase.

When to Activate

User asks how a system or feature works
User is onboarding to a new codebase
User needs to understand how components connect
User asks about architecture, data flow, or system design
User is making changes that span multiple modules and needs context

How to Use

Detect the current repository from git remote: git remote get-url origin
Call list_wiki_pages with the owner and repo to discover available documentation
Find wiki pages relevant to the user's question by matching page titles and descriptions
Call get_wiki_page for the most relevant pages
Synthesize the wiki content into a focused answer for the user's specific question

Presentation

Summarize the relevant wiki content, don't dump the entire page
Reference specific wiki pages so the user can explore further
Connect wiki knowledge to the specific files or modules the user is working with
If no wiki exists for this repo, suggest the user set one up in the cubic dashboard

Source

git clone https://github.com/mrge-io/cubic-claude-plugin/blob/main/skills/codebase-context/SKILL.mdView on GitHub

Overview

This skill pulls architectural context from cubic's AI-generated wiki to explain how the codebase fits together. It helps users understand system design, data flow, and onboarding by surfacing targeted wiki pages and synthesizing them into concise, actionable guidance.

How This Skill Works

It determines the current repository from the git remote, lists available wiki pages with list_wiki_pages, selects the most relevant pages by matching titles and descriptions, fetches content via get_wiki_page, and then synthesizes a focused answer that ties the wiki content to the user's files or modules.

When to Use It

User asks how a system or feature works
User is onboarding to a new codebase
User needs to understand how components connect
User asks about architecture, data flow, or system design
User is making changes that span multiple modules and needs context

Quick Start

Step 1: Detect the current repository from git remote: git remote get-url origin
Step 2: Call list_wiki_pages with the owner and repo to discover available documentation
Step 3: Call get_wiki_page for the most relevant pages and synthesize a focused answer

Best Practices

Summarize the relevant wiki content, don't dump the entire page
Reference specific wiki pages so the user can explore further
Connect wiki knowledge to the specific files or modules the user is working with
Keep explanations concise and tailored to the user's question
If no wiki exists for the repo, suggest setting one up in the cubic dashboard

Example Use Cases

Explain how the authentication flow works across modules in the codebase
Onboard a new developer by outlining the overall architecture and module responsibilities
Describe data flow between services X and Y to clarify integration points
Clarify system design decisions behind a feature and why artifacts are organized as they are
Trace how a bug in feature Z could impact multiple modules and where to look first

Frequently Asked Questions

Add this skill to your agents