Analyze contract diffs and report impacted tasks and code paths.
npx skills add https://github.com/ezagent42/prd2impl --skill contract-check
Please help me install this Agent Skill. Skill: contract-check Source: https://github.com/ezagent42/prd2impl/tree/main/skills/skill-12-contract-check Command: npx skills add https://github.com/ezagent42/prd2impl --skill contract-check
Contract changes can ripple through a project; this skill analyzes contract/interface changes and flags affected tasks and code.
Run the contract-check workflow to evaluate recent diffs and identify affected tasks.
High-intent search queries and answers about installing and using this skill.
To detect contract drift, you analyze git diffs against contract definitions and interface schemas to identify breaking changes. This process cross-references modified API schemas or interface definitions with plan tasks to surface affected code paths.
Contract drift occurs when changes in interface definitions or API schemas diverge from expected dependencies, causing code impact. It ripples through projects by silently breaking dependent code paths and invalidating previously mapped plan tasks.
Assessing the impact of API schema changes requires cross-referencing the modified schema definitions with existing plan tasks. The analysis maps interface modifications to dependent code paths to generate a report detailing affected tasks.
Yes, you can map changes in interface definitions to specific code paths by parsing the contract files and reading the git diffs. This cross-referencing identifies exactly which dependent code paths and tasks the interface modifications affect.
The best way to analyze diffs in docs/contracts is to parse the contract definitions and cross-reference them with project plan tasks. This approach evaluates recent diffs to surface affected code paths and produces a comprehensive impact report.
Yes, existing plan tasks are required to cross-reference contract changes and output an accurate impact report. The analysis maps modifications from parsed contract files and git diffs directly against these predefined plan tasks to identify affected code.
vladm3105Create Layer 9 Data Contracts with Markdown and YAML files.
FernanSuozaAnalyze change impacts across requirements, design, stories, tests, and release scope.
TeamSloppyGenerate executable software-engineering plans without altering source code.
jamon8888Navigate GitNexus MCP tools, resources, and knowledge graph schema.
