adapters
FreeSkill for the Adapters area of paddock. 108 symbols across 22 files.
The English summary is being prepared. Showing the original description.
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
1. READ gitnexus://repos → Discover indexed repos
2. READ gitnexus://repo/{name}/context → Codebase overview, check staleness
3. gitnexus_query({query: "<what you want to understand>"}) → Find related execution flows
4. gitnexus_context({name: "<symbol>"}) → Deep dive on specific symbol
5. READ gitnexus://repo/{name}/process/{name} → Trace full execution flow
If step 2 says "Index is stale" → run
direnv exec . gitnexus analyze --embeddings --skip-agents-mdfrom this repo root after the LM Studio embedding server is running.
- [ ] READ gitnexus://repo/{name}/context
- [ ] gitnexus_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] gitnexus_context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details
| Resource | What you get |
|---|---|
gitnexus://repo/{name}/context | Stats, staleness warning (~150 tokens) |
gitnexus://repo/{name}/clusters | All functional areas with cohesion scores (~300 tokens) |
gitnexus://repo/{name}/cluster/{name} | Area members with file paths (~500 tokens) |
gitnexus://repo/{name}/process/{name} | Step-by-step execution trace (~200 tokens) |
gitnexus_query — find execution flows related to a concept:
gitnexus_query({query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locations
gitnexus_context — 360-degree view of a symbol:
gitnexus_context({name: "validateUser"})
→ Incoming calls: loginHandler, apiMiddleware
→ Outgoing calls: checkToken, getUserById
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
1. READ gitnexus://repo/my-app/context → 918 symbols, 45 processes
2. gitnexus_query({query: "payment processing"})
→ CheckoutFlow: processPayment → validateCard → chargeStripe
→ RefundFlow: initiateRefund → calculateRefund → processRefund
3. gitnexus_context({name: "processPayment"})
→ Incoming: checkoutHandler, webhookHandler
→ Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Skill for the Adapters area of paddock. 108 symbols across 22 files.
The English summary is being prepared. Showing the original description.
Skill for the Chat area of paddock. 62 symbols across 10 files.
The English summary is being prepared. Showing the original description.
Skill for the Dashboard area of paddock. 80 symbols across 16 files.
The English summary is being prepared. Showing the original description.
Skill for the Github area of paddock. 23 symbols across 5 files.
The English summary is being prepared. Showing the original description.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
The English summary is being prepared. Showing the original description.
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
The English summary is being prepared. Showing the original description.