Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
A skill your agent uses when the user is debugging a bug, tracing an error, or asking why something fails.
Install Gitnexus Debugging
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-debugging .claude/skills/gitnexus-debugging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gitnexus-debugging" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debugging into .claude/skills/gitnexus-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-debugging .agents/skills/gitnexus-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gitnexus-debugging" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debugging into .agents/skills/gitnexus-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-debugging .cursor/skills/gitnexus-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gitnexus-debugging" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debugging into .cursor/skills/gitnexus-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws-samples/sample-kolya-br-proxy.git --path .claude/skills/gitnexus/gitnexus-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-debugging .gemini/skills/gitnexus-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gitnexus-debugging" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debugging into .gemini/skills/gitnexus-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-debugging .github/skills/gitnexus-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gitnexus-debugging" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debugging into .github/skills/gitnexus-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-debugging .opencode/skills/gitnexus-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gitnexus-debugging" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-debugging into .opencode/skills/gitnexus-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gitnexus-debugging- GitHub stars
- 106
- Used in
- 11 other repos
- Token cost
- ~780 tokens
- SKILL.md length
- 122 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT-0
At a glance
A skill your agent uses when the user is debugging a bug, tracing an error, or asking why something fails.
- The user is debugging a bug
- SKILL.md covers When to Use, Workflow, Checklist and Debugging Patterns, plus 2 more sections
- Calls npx
- Tracing an error
What it does
Gitnexus Debugging is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. 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"
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The licence is MIT-0.
When your agent uses it
- The user is debugging a bug
- Tracing an error
- Asking why something fails
Example prompts
- “Why is X failing?”
- “Where does this error come from?”
- “Trace this bug”
- “/gitnexus-debugging”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 9c3dcee. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Gitnexus Debugging loads about 780 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 122 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws-samples/sample-kolya-br-proxy at commit 9c3dcee, republished under its MIT-0 licence (© aws-samples). 122 words, ~780 tokens.
Download SKILL.mdSave it as
.claude/skills/gitnexus-debugging/SKILL.md (or your agent's skills folder).- name
- gitnexus-debugging
- 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"
Debugging with GitNexus
When to Use
- "Why is this function failing?"
- "Trace where this error comes from"
- "Who calls this method?"
- "This endpoint returns 500"
- Investigating bugs, errors, or unexpected behavior
Workflow
1. gitnexus_query({query: "<error or symptom>"}) → Find related execution flows
2. gitnexus_context({name: "<suspect>"}) → See callers/callees/processes
3. READ gitnexus://repo/{name}/process/{name} → Trace execution flow
4. gitnexus_cypher({query: "MATCH path..."}) → Custom traces if neededIf "Index is stale" → run
npx gitnexus analyzein terminal.
Checklist
- [ ] Understand the symptom (error message, unexpected behavior)
- [ ] gitnexus_query for error text or related code
- [ ] Identify the suspect function from returned processes
- [ ] gitnexus_context to see callers and callees
- [ ] Trace execution flow via process resource if applicable
- [ ] gitnexus_cypher for custom call chain traces if needed
- [ ] Read source files to confirm root causeDebugging Patterns
| Symptom | GitNexus Approach |
|---|---|
| Error message | gitnexus_query for error text → context on throw sites |
| Wrong return value | context on the function → trace callees for data flow |
| Intermittent failure | context → look for external calls, async deps |
| Performance issue | context → find symbols with many callers (hot paths) |
| Recent regression | detect_changes to see what your changes affect |
Tools
gitnexus_query — find code related to error:
gitnexus_query({query: "payment validation error"})
→ Processes: CheckoutFlow, ErrorHandling
→ Symbols: validatePayment, handlePaymentError, PaymentExceptiongitnexus_context — full context for a suspect:
gitnexus_context({name: "validatePayment"})
→ Incoming calls: processCheckout, webhookHandler
→ Outgoing calls: verifyCard, fetchRates (external API!)
→ Processes: CheckoutFlow (step 3/7)gitnexus_cypher — custom call chain traces:
MATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: "validatePayment"})
RETURN [n IN nodes(path) | n.name] AS chainExample: "Payment endpoint returns 500 intermittently"
1. gitnexus_query({query: "payment error handling"})
→ Processes: CheckoutFlow, ErrorHandling
→ Symbols: validatePayment, handlePaymentError
2. gitnexus_context({name: "validatePayment"})
→ Outgoing calls: verifyCard, fetchRates (external API!)
3. READ gitnexus://repo/my-app/process/CheckoutFlow
→ Step 3: validatePayment → calls fetchRates (external)
4. Root cause: fetchRates calls external API without proper timeout© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/gitnexus/gitnexus-debugging of aws-samples/sample-kolya-br-proxy.
Open the folder on GitHubat commit 9c3dcee
Used in 12 other repositories
We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in aws-samples/sample-kolya-br-proxy, which our catalogue first saw on October 7, 2026.
- ML4ITS/TimeVQVAE.agents/skills/gitnexus/debugging
- kunwarVivek/mcp-github-project-manager.agents/skills/gitnexus-debugging
- Arenukvern/mcp_flutter.claude/skills/gitnexus/gitnexus-debugging
- BA-CalderonMorales/terminal-jarvis.agents/skills/gitnexus/gitnexus-debugging
- ceilf6/FrontAgent.agents/skills/gitnexus/gitnexus-debugging.claude/skills/gitnexus/gitnexus-debugging
- Sayhi-bzb/CharDesk.agents/skills/gitnexus/gitnexus-debugging
- mindfold-ai/Trellis.claude/skills/gitnexus/gitnexus-debugging
- TabularisDB/tabularis.claude/skills/gitnexus/gitnexus-debugging
- ucsandman/DashClaw.agents/skills/gitnexus-debugging.claude/skills/gitnexus-debugging
- Apra-Labs/apra-fleet.claude/skills/gitnexus/gitnexus-debugging
- Sayhi-bzb/Agent-HTML.claude/skills/gitnexus/gitnexus-debugging
- NeverSight/learn-skills.devdata/skills-md/abhigyanpatwari/gitnexus/gitnexus-debugging
Compare with similar skills
Gitnexus Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gitnexus Debugging this skillaws-samples/sample-kolya-br-proxy | 106 | 11 repos | ~780 | Automated safety check: Pass | MIT-0 | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Debuggingultralisp/ultralisp | 258 | 51 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
More from aws-samples/sample-kolya-br-proxy
- Official
Gitnexus Exploring
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
- Official
Gitnexus Impact Analysis
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user wants to know what will break if they change something, or needs safety analysis before editing code.
- Official
Gitnexus Refactoring
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user wants to rename, extract, split, move, or restructure code safely.
- Official
Gitnexus CLI
aws-samples/sample-kolya-br-proxy
A skill your agent uses 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.
- Official
Gitnexus Guide
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference.
Related
Categories
Questions about Gitnexus Debugging
What does Gitnexus Debugging do?
A skill your agent uses when the user is debugging a bug, tracing an error, or asking why something fails. Gitnexus Debugging is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. Use when the user is debugging a bug, tracing an error, or asking why something fails.
When should I use Gitnexus Debugging?
Gitnexus Debugging fits situations like: the user is debugging a bug; tracing an error; asking why something fails.
How do I install Gitnexus Debugging in Claude Code?
Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a claude-code`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-debugging in aws-samples/sample-kolya-br-proxy) into .claude/skills/gitnexus-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Gitnexus Debugging in Codex?
Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a codex`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-debugging in aws-samples/sample-kolya-br-proxy) into .agents/skills/gitnexus-debugging in your project. Codex loads it when a task matches its description.
Can I use Gitnexus Debugging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitnexus-debugging, .gemini/skills/gitnexus-debugging, .github/skills/gitnexus-debugging and .opencode/skills/gitnexus-debugging in your project.
What does Gitnexus Debugging need to run?
Going by SKILL.md and its folder, Gitnexus Debugging needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Gitnexus Debugging access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Gitnexus Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Gitnexus Debugging use?
Gitnexus Debugging is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Gitnexus Debugging use?
About 780 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Gitnexus Debugging?
Skills that share tags, products or a category with Gitnexus Debugging: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gitnexus Debugging?
aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/sample-kolya-br-proxy, which has 106 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.
Source: aws-samples/sample-kolya-br-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.