All authors
Claude Skills by ReidenXerx
github.com/ReidenXerx30 skills0 installs59 views
- Bearing Api RoutesHTTP API route changes. Use api_impact/route_map/shape_check on framework routers (Express/Fastify/Hono/Next); use graph tools on dispatcher symbols when the project has a custom hand-rolled router (no indexed Route nodes). Examples: add endpoint, change route, trace handler + consumers.Votes: 0GitHub stars: 6
- Bearing Architecture ReviewUse to JUDGE structure — coupling, cohesion, layering violations, import cycles, god objects. Exploring/imaging help you understand; this produces an assessment with evidence. Examples: \"review the architecture\", \"where's the coupling\", \"are there layering violations\", \"find import cycles / god objects\".Votes: 0GitHub stars: 6
- Bearing CliUse 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\"Votes: 0GitHub stars: 6
- Bearing ConsultDecide WHEN to ask the human and when to just decide — so a senior engineer is interrupted for things that actually change the product, and never for boring technical essentials. Use when you notice you are about to INVENT a requirement rather than implement one, when two readings of the request lead to materially different work, or before a ONE-WAY DOOR (deleting data, pushing, publishing, migrating). NOT for questions the repo can answer, not for permission you already have, not to offload ...Votes: 0GitHub stars: 6
- Bearing DebuggingUse 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\"Votes: 0GitHub stars: 6
- Bearing E2eUse when verifying app behaviour in a real browser, or when the user asks for a screenshot of a page/view. Covers writing a verifier in .e2e/, testing a destructive write without performing it, and capturing shots. Examples: \"check the payer editor works\", \"screenshot the dashboard\", \"does this button send the right payload\", \"verify the fix end to end\".Votes: 0GitHub stars: 6
- Bearing EnforcementNorth-star tool router when GitNexus hooks block Grep/Read/SemanticSearch. Graph + embeddings + cypher reasoning, autonomous refresh when stale, classical fallback when GN fails.Votes: 0GitHub stars: 6
- Bearing ExploringUse 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\"Votes: 0GitHub stars: 6
- Bearing Feature DevUse when ADDING new code — implement a feature, add an endpoint/handler, wire in a new module. The graph finds existing patterns to reuse and the right place to integrate. Examples: \"add a feature that does X\", \"where do I wire this in\", \"implement X like the existing Y\", \"add a new endpoint\".Votes: 0GitHub stars: 6
- Bearing GuideUse when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"Votes: 0GitHub stars: 6
- Bearing ImagingGraph-first mental models for pipelines, call chains, and cross-module flows. Use when explaining architecture, tracing business flows, mapping functional areas, or answering "how does X connect to Y?" — never reconstruct structure from grep.Votes: 0GitHub stars: 6
- Bearing Impact AnalysisUse when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"Votes: 0GitHub stars: 6
- Bearing Layered SystemsUse when WORKING IN a complex, multi-layered architecture — trace a request through layers (controller→service→repo→model), change at the right layer, and respect boundaries/contracts between layers. For monoliths, hexagonal/onion, and monorepos with packages. Examples: \"trace this request through the layers\", \"which layer should I change\", \"what crosses this boundary\", \"change the DTO between service and API safely\".Votes: 0GitHub stars: 6
- Bearing LocalCompressed GitNexus playbook for local/Ollama models in Zed — graph-first with minimal context overhead. Use when running qwen/deepseek/llama via Ollama.Votes: 0GitHub stars: 6
- Bearing MicroscopeDeep multi-lens audit ('microscope waves') for MILESTONE moments — feature done / big-task checkpoint / shared-code refactor / pre-ship, or when asked to 'audit / find real bugs / is this solid'. NOT for small localized changes. Goes beyond cascade code-review: it opinionates (relevance, soundness, over-engineering) as a senior domain expert, verifies findings adversarially, and iterates in waves. Examples: \"microscope this\", \"audit before we ship\", \"find the real oversights\", \"deep re...Votes: 0GitHub stars: 6
- Bearing MinionsFan work out to a swarm of cheap, anchored subagents that GATHER — for wide mechanical work you would otherwise grind through serially: finding every call site, auditing N files against one rule, discovering migration sites, cross-referencing a list against the codebase, 'where is this used and how does it flow'. Use when the work is bounded, verifiable, independent and wide (3+ units). NOT when the judgment IS the work, when the answer only survives verbatim, or when the unit needs conversat...Votes: 0GitHub stars: 6
- Bearing NorthstarsRead, cite, and maintain the project's north-stars — the authoritative numbered fixed points (invariants, exact term meanings, evidence standards, settled decisions, graveyard) that outrank every other doc and stop semantic drift. Use when starting work on a project that has .bearing/northstars.md, when a re-anchor fires, when a doc/code conflicts with a north-star, when proposing or rejecting an idea, or when drafting/updating the north-stars themselves.Votes: 0GitHub stars: 6
- Bearing PerformanceUse when optimizing a slow path or reasoning about cost/hot paths. GitNexus reveals call STRUCTURE (depth, fan-in, repeated work) — pair with a real profiler for runtime numbers. Examples: \"this endpoint is slow\", \"find the hot path\", \"why is this expensive\", \"reduce redundant work\".Votes: 0GitHub stars: 6
- Bearing Pr ReviewUse when reviewing a pull request, understanding what a PR changes, assessing merge risk, or checking test coverage gaps. Examples: \"Review this PR\", \"What does PR #42 change?\", \"Is this PR safe to merge?\"Votes: 0GitHub stars: 6
- Bearing PrUse when opening a pull request, writing or improving a PR description, or preparing a branch for review. Examples: \"Open a PR for this\", \"Write the PR description\", \"Is this branch ready to review?\". For reviewing SOMEONE ELSE'S PR, use bearing-pr-review instead.Votes: 0GitHub stars: 6
- Bearing RefactoringUse when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"Votes: 0GitHub stars: 6
- Bearing ScenariosScenario playbooks for GitNexus — pre-edit, pre-commit, PR review, bugs, refactors, cross-module changes, presets. Read when starting a structured task.Votes: 0GitHub stars: 6
- Bearing Security ReviewUse for security-sensitive changes, taint/source-to-sink questions, injection risk, path traversal, XSS, command/code/sql injection, auth/input/file/db/exec reviews.Votes: 0GitHub stars: 6
- Bearing TaskcoreMaintain a dense, AI-facing TASK-CORE save-state so a long task survives context COMPACTION without drift. Load it when: a PostToolUse nudge says edits have accumulated since the core was last written, at a milestone / before a risky pivot / when the task shifts, OR on recovery after a compaction (read it back first). The core is for the model, not humans — terse, anchors over prose. Examples: \"context is filling — save state\", \"update the task core\", \"clean it from log-like things but k...Votes: 0GitHub stars: 6
- Bearing TestingUse when deciding WHAT to test or checking coverage. The graph turns blast radius into a precise test target list and surfaces untested symbols. Examples: \"what should I test for this change\", \"is this covered\", \"write tests for X\", \"which flows need tests\".Votes: 0GitHub stars: 6
- Bearing WorkspaceMaster index for __GITNEXUS_REPO__ GitNexus usage in Cursor. Use at the start of any code task — exploration, edits, refactors, PR review, or API changes. Teaches workflow chain, anti-patterns, and which skill to load.Votes: 0GitHub stars: 6
- Bearing FrontendStructure UI as reusable components, and treat editing a shared one as the multi-screen change it is. Use when about to write layout markup that encloses other content — a table, a bordered panel, a card, a modal shell, a toolbar — when deciding whether an existing component fits, or when a change to a shared component would alter what existing callers render. Examples: \"add a table to this page\", \"wrap this in a bordered box\", \"can I add a prop to Panel?\", \"is there already a componen...Votes: 0GitHub stars: 6
- Bearing Invasive MinionsFan out a DECIDED, mechanical code change across many independent sites at once, instead of grinding them one at a time — logging coverage, error handling, a settled API migration, adding a guard clause everywhere a shape is unwrapped. Each subagent EDITS its own disjoint slice and returns the diff it wrote. Use when the transformation is already decided, the sites are 3+ and independent, and no two slices touch the same file. NOT when the change differs per site in a way that needs judgment,...Votes: 0GitHub stars: 6
- Bearing ReactReact specifics that type-check, run, and are still wrong — starting with react-hook-form, where a field component owns its Controller and a `name` typed as string can drop a value from the submitted form with no error anywhere. Use when building or reviewing a form input, wrapping a controlled component for a form library, naming a field in setValue/watch/getValues, or when a form submits without a field's value. Examples: \"add a text field to this form\", \"wrap this select for react-hook-...Votes: 0GitHub stars: 6
- Bearing TsjsWrite and review TypeScript/JavaScript that is not merely type-correct — the traps that compile clean, lint clean, and are still wrong at runtime. Use when writing or editing non-trivial .ts/.tsx/.js/.jsx, when reviewing a TS/JS diff, when data enters the program (fetch, JSON.parse, env, DB row, message), when reaching for `as` or `any` to make an error go away, when adding a member to a union, or when async work is involved. Examples: \"is this `as` safe?\", \"any or unknown here?\", \"why i...Votes: 0GitHub stars: 6