code-integration

Analyze integration seams between local symbols and external dependencies.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill code-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-integration
Source: https://github.com/getspur/spur/tree/main/assets/skills/code-integration
Command: npx skills add https://github.com/getspur/spur --skill code-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity and risk associated with integrating third-party dependencies into a codebase by providing a structured, evidence-based framework for verifying the connection between local symbols and external contracts.

Core Features & Use Cases

  • Paired-Seam Analysis: Simultaneously evaluates local implementation and external dependency behavior to ensure contract alignment.
  • Revision-Aware Verification: Enforces the use of specific, locked dependency versions to prevent compatibility drift.
  • Use Case: When implementing a custom Serde trait or wrapping an external SDK, use this skill to prove that your local error handling, type mapping, and lifecycle assumptions match the exact version of the library defined in your lockfile.

Quick Start

Use the code-integration skill to trace the seam between the local symbol for the authentication wrapper and the corresponding external SDK method pinned in the lockfile.

Frequently Asked Questions about code-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify API contract compatibility between local code and external dependencies?

Paired-seam analysis evaluates local implementations against external SDK behavior simultaneously, proving that your type mapping and error handling match the specific locked dependency version defined in your lockfile.

Can I check FFI boundary alignment and trait implementations against third-party libraries?

Yes, you can analyze FFI boundaries and trait implementations like custom Serde traits by applying revision-aware verification to prove your local lifecycle assumptions match the targeted external library contract.

How do I prevent dependency version drift when integrating an external SDK wrapper?

You prevent dependency version drift by enforcing revision-aware verification, which requires strict adherence to revision-pinned evidence from your lockfile during static analysis of the integration seam.

What are the limitations of static analysis for local-external code integration seams?

Static analysis of integration seams requires strict adherence to revision-pinned evidence and precise lockfile versions, meaning dynamic runtime behaviors or unpinned dependencies may fall outside its depth-first tracing scope.