gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code.
How it works
What gitnexus-impact-analysis does
Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\".
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
A finished result to review
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about gitnexus-impact-analysis
Updated Sep 2, 2026.
What does gitnexus-impact-analysis do?
Use 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?\"
Who is gitnexus-impact-analysis for?
It is designed for teams that want to hand off recurring work and review the result before it is used.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does gitnexus-impact-analysis produce?
A finished result to review. Results come back with their sources and any open questions for you to check before anything is used.
How much does gitnexus-impact-analysis cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmtkm9cok0008…
- Sep 2, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- abhigyanpatwari/GitNexus
- License
- NOASSERTION
Connections
Where gitnexus-impact-analysis fits
Similar skills5
Agent Progress Assessor
Compare an agent's reported work with authoritative before-and-after evidence to recommend whether progress is real, stale, blocked, or needs review. Use for agent supervision; do not use to mark work complete or grant approval.FreeSkill · AI & Agent ToolingClassify and Route
Classify supplied content into a caller-approved finite set of destinations and return a confidence-aware routing recommendation. Use for support triage, inbox tagging, document queues, or analytics schema-domain selection when Relay's structured-decision tool is available; do not use for open-ended answers or unapproved actions.FreeSkill · AI & Agent ToolingSource Claim Verifier
Screen factual claims against supplied, versioned source passages and produce a citation-preserving review register. Use for research, reports, and agent output verification; do not treat a model score as proof or search for missing evidence without authorization.FreeSkill · AI & Agent Toolinggitnexus-review
Review code changes with GitNexus from a GitHub PR URL or number, a branch/ref or commit range, or local staged, unstaged, and untracked changes. Use when the user asks for a code review, merge-risk assessment, regression hunt, missing-test analysis, or a verdict on whether a PR, branch, commit range, or local diff is safe.FreeCommunitySkill · AI & Agent ToolingAnalytics Domain Router
Recommend an approved analytics data domain for a question using a versioned domain catalog. Use before query planning when several authorized domains could fit; do not use to reveal schemas, write SQL, or grant data access.FreeHave a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.