integration-impact — for Claude Code integration-impact, agent-delivery-pub, community, for Claude Code, ide skills, Purpose, downstream, consumers, changed, interface

v1.0.0
GitHub

Sobre este Skill

Perfeito para Agentes de Integração de Sistema que necessitam de análise avançada de impacto de alterações de API. Resumo localizado: Assesses downstream consumer impact of API, event, or shared service changes. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Recursos

context-core/variable/integration-registry.md — Registered integrations and consumers
context-core/variable/dependency-map.md — System dependency graph
Step 1: Identify Changed Interfaces
Accept a description of the proposed change: which API endpoints, event schemas, shared services
Assesses downstream consumer impact of API, event, or shared service changes

# Core Topics

for Claude Code Purpose downstream consumers changed interface
tgsatwit tgsatwit
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
50
Canonical Locale
en
Detected Body Locale
en

Perfeito para Agentes de Integração de Sistema que necessitam de análise avançada de impacto de alterações de API. Resumo localizado: Assesses downstream consumer impact of API, event, or shared service changes. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Por que usar essa habilidade

Habilita os agentes a avaliar o impacto das alterações propostas de API nos consumidores downstream usando integrações registradas e gráficos de dependência do sistema, garantindo que não haja surpresas ou quebras por meio de uma análise abrangente de conteúdo de dados de registro de integração e

Melhor para

Perfeito para Agentes de Integração de Sistema que necessitam de análise avançada de impacto de alterações de API.

↓ Casos de Uso Práticos for integration-impact

Analisar alterações de pontos de extremidade de API para quebras de consumidores downstream
Mapear gráficos de dependência do sistema para atualizações de esquema de eventos propostas
Avaliar alterações de serviços compartilhados para compatibilidade de integração registrada

! Segurança e Limitações

  • Requer acesso a dados do registro de integração
  • Necessita de informações do gráfico de dependência do sistema
  • Limitado à análise de alterações propostas dentro de integrações registradas

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is integration-impact?

Perfeito para Agentes de Integração de Sistema que necessitam de análise avançada de impacto de alterações de API. Resumo localizado: Assesses downstream consumer impact of API, event, or shared service changes. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install integration-impact?

Run the command: npx killer-skills add tgsatwit/agent-delivery-pub/integration-impact. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for integration-impact?

Key use cases include: Analisar alterações de pontos de extremidade de API para quebras de consumidores downstream, Mapear gráficos de dependência do sistema para atualizações de esquema de eventos propostas, Avaliar alterações de serviços compartilhados para compatibilidade de integração registrada.

Which IDEs are compatible with integration-impact?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for integration-impact?

Requer acesso a dados do registro de integração. Necessita de informações do gráfico de dependência do sistema. Limitado à análise de alterações propostas dentro de integrações registradas.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add tgsatwit/agent-delivery-pub/integration-impact. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use integration-impact immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

integration-impact

Resumo localizado: Assesses downstream consumer impact of API, event, or shared service changes. This AI agent skill supports Claude Code, Cursor, and

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Purpose

Map all downstream consumers of a changed interface and assess the impact of the proposed change so that no consumer is surprised by breakages.

Context to Load

  1. context-core/variable/integration-registry.md — Registered integrations and consumers
  2. context-core/variable/dependency-map.md — System dependency graph

Workflow

Step 1: Identify Changed Interfaces

Accept a description of the proposed change: which API endpoints, event schemas, shared services, data contracts, or libraries are being modified. Classify each change as: addition, modification, deprecation, or removal.

Step 2: Map Downstream Consumers

For each changed interface, enumerate all known consumers from the integration registry and dependency map:

  • Direct consumers: Systems that call the API or subscribe to the event
  • Transitive consumers: Systems that depend on direct consumers and may be affected
  • Internal consumers: Teams within the organisation
  • External consumers: Third-party integrations, partner systems

Flag any interfaces not registered in the integration registry (shadow integrations).

Step 3: Classify Impact per Consumer

Impact LevelDefinitionAction Required
BreakingConsumer will fail without changesMigration plan required before deployment
BehaviouralConsumer will not fail but behaviour changesNotification and testing required
AdditiveNew capability, no existing behaviour changedNotification only
NoneConsumer is unaffectedNo action

Step 4: Assess Migration Effort

For each consumer with Breaking or Behavioural impact, estimate:

  • Code changes required (trivial/moderate/significant)
  • Testing effort (smoke test/regression suite/full retest)
  • Coordination needed (async notification/sync alignment/joint release)
  • Timeline (same sprint/next sprint/multi-sprint)

Step 5: Generate Impact Matrix

Output a matrix: Consumer, Interface, Change Type, Impact Level, Migration Effort, Coordination, Owner. Include a summary: total consumers affected, breaking changes count, estimated total migration effort.

Step 6: Recommend Mitigation Strategy

Based on impact analysis, recommend:

  • Versioning strategy (if breaking changes affect many consumers)
  • Migration timeline and sequencing
  • Feature flag approach (if gradual rollout is feasible)
  • Communication plan for affected teams

Intent Alignment

  • Every consumer must be accounted for — unknown consumers are the highest risk
  • Breaking changes require explicit migration plans, not just notifications
  • Additive changes are preferred over modifications — extend, do not modify
  • Shadow integrations (unregistered consumers) must be flagged, not ignored

Escalation Triggers

  • Breaking change affects more than 3 downstream consumers
  • External consumer is affected by a breaking change
  • Shadow integrations are discovered (unregistered consumers)
  • Migration timeline exceeds the deployment window
  • Changed interface touches payment, auth, or compliance systems

Input

$ARGUMENTS

Habilidades Relacionadas

Looking for an alternative to integration-impact or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumo localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
Inteligência Artificial

nextjs-turbopack

[ Destaque ]
Logo of affaan-m
affaan-m

Resumo localizado: Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack. It covers ai-agents, anthropic, claude workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 169.5k
⑂ 0
Produtividade

widget-generator

Logo of f
f

Resumo localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

★ 149.6k
⑂ 0
Inteligência Artificial

flags

Logo of vercel
vercel

Resumo localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
Navegador