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
Skill: Impact Analysis (Python)
Implements: SYSP_SPEC_SKILL_IMPACT_QUERY, SYSP_SPEC_SKILL_IMPACT_EXCHANGE, SYSP_SPEC_SKILL_IMPACT_GROUP Requirements: SYSP_REQ_SKILL_IMPACT_QUERY, SYSP_REQ_SKILL_IMPACT_EXCHANGE, SYSP_REQ_SKILL_IMPACT_GROUP
Instructions
Tool
.github/skills/syspilot.impact-python/scripts/get_need_links.py — run with --help for parameter details.
Requires docs/_build/html/needs.json — run sphinx-build first if stale.
Exchange Contract
To replace this implementation: create a new skill folder, provide the same
query-by-ID capability, update the description for Copilot discovery.
No agent changes required.
Rules
Mandatory Execution
Impact Analysis is mandatory for every change. File lists provided in a Change Request are input hints, not the complete scope. This skill MUST be executed before any spec changes are made — the result defines the actual scope.
1. Search from consumer elements, not from new elements
A newly created element has no incoming links. Run the query from each consumer element that the new element satisfies.
Example: You created SYSP_US_SKILL_IMPACT which :links: to SYSP_US_DESIGN
and SYSP_US_PM. Run the impact query from SYSP_US_DESIGN and SYSP_US_PM
(not from the new US).
2. Use --direction in for level transitions
in = "who links to me" = "who implements me at the next level down".
REQs link upward to USes, SPECs link upward to REQs. So querying a US with
--direction in yields its REQ candidates.
3. Depth strategy
| Transition | Depth | Rationale |
|---|---|---|
| Level 0 → Level 1 | 1 | US → REQ, direct links |
| Level 1 → Level 2 | 1 | REQ → SPEC, direct links |
| Level 2 cross-check | 2 | Catches second-order consumers (e.g. doc SPECs aggregating workflow SPECs) |
4. Raw output at Level 0, assessment at Level 1/2
At Level 0 present candidates to the user without verdicts. Assessment (affected / not affected) happens when writing the next level.
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 | 1mo | Review | Advanced |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| cc-skill-project-guidelines-example | 1 | 6mo | Review | Beginner |
| mcp-builder | 136 | 3mo | 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