syspilot.impact-python
Analyzes technical specification links to determine the impact of changes across a system.
Install
mkdir -p .claude/skills/syspilot-impact-python && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10202" && unzip -o skill.zip -d .claude/skills/syspilot-impact-python && rm skill.zipInstalls to .claude/skills/syspilot-impact-python
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Impact analysis using sphinx-needs dependency trees. Discovers affected specification elements by traversing traceability links. USE FOR: change scoping, blast radius analysis, element discovery before spec writing.Key capabilities
- →Traverse traceability links
- →Find affected specification elements
- →Analyze blast radius
- →Query consumer/producer relationships
How it works
It traverses sphinx-needs dependency trees to discover elements affected by a proposed change.
Inputs & outputs
When to use syspilot.impact-python
- →Determine change impact
- →Analyze blast radius of code changes
- →Discover linked specification elements
- →Validate documentation dependencies
About this skill
Impact Analysis
Tool
Run .github/skills/syspilot.impact-python/scripts/get_need_links.py --help for the complete CLI.
python .github/skills/syspilot.impact-python/scripts/get_need_links.py NEED_ID --direction both --depth 2
The default inputs are:
- active ontology: the literal
needs_from_tomlstring indocs/conf.py, resolved relative to that configuration file; - built per-ID Needs data:
docs/_build/html/needs_id/.
Use --ontology or --needs-dir to override these inputs. Configuration is inspected without executing it; use --ontology when needs_from_toml is computed rather than a literal string. Missing or invalid bindings fail explicitly. The tool attempts a Sphinx HTML build when default Needs data is absent; use --no-build when the caller must control that prerequisite.
Traversal
The tool reads every option declared by the active ontology's [[needs.extra_links]]. It traverses each <option> and <option>_back field in addition to standard links and links_back, so customer-defined link types work without code changes.
--direction outfollows outgoing fields.--direction infollows incoming*_backfields.--direction bothfollows both.--depth Nbounds traversal depth.--flatreturns sorted unique linked IDs.--simplereturns direct incoming and/or outgoing IDs plus metadata.--typedreturns relationship pairs withsource,target,option, direction, and discovery depth for analyzers such as Trace.- Default output is a nested tree with cycle/repeated-node truncation.
Typed output is opt-in; without it, the existing nested, flat, and simple formats are unchanged. IDs reached through multiple link options are de-duplicated. Cycles do not recurse indefinitely.
Contract Use
Run impact analysis from existing elements whose relationships can expose affected work. Query output supplies candidate scope and traceability evidence to the applicable Contract. The Contract records the disposition of each candidate and remains authoritative for included artifacts, responsibility, and scope decisions.
Do not treat an empty or failed query as authoritative evidence. The command exits non-zero for an unknown Need, missing or invalid ontology, missing built Needs data, or an unusable build prerequisite. Resolve the reported prerequisite before recording impact conclusions.
Verification
Release QA is maintained in Syspilot's repository test suite, outside the installed skill folder.
When not to use it
- →When the sphinx-needs documentation is stale
Prerequisites
Limitations
- →Requires sphinx-build to be run
- →Requires valid traceability links
How it compares
It automates impact analysis based on formal traceability links, rather than manual dependency tracking.
Compared to similar skills
syspilot.impact-python side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| syspilot.impact-python (this skill) | 0 | 5mo | Review | Advanced |
| deepwiki-rs | 25 | 1y | Review | Intermediate |
| cc-skill-project-guidelines-example | 1 | 9mo | Review | Beginner |
| mcp-builder | 136 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
cc-skill-project-guidelines-example
davila7
Project Guidelines Skill (Example)
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools