dependency-ci-contract

Validates dependency and lockfile changes against CI typecheck and build gates.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill dependency-ci-contract-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-ci-contract
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/generated/dependency-ci-contract
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill dependency-ci-contract-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dependency updates and lockfile regenerations frequently break typecheck, build, or test pipelines, and teams waste review cycles chasing failures caused by unsynced environments rather than actual code defects. ## Core Features & Use Cases - CI Gate Enforcement: Requires typecheck and build to pass locally before any dependency change is presented for review. - Environment Baseline Verification: Mandates confirming node_modules matches the lockfile (via npm ci) before attributing test failures to code. - Role-Based Checklists: Provides reviewer and test engineer checklists covering lockfile sync, TypeScript version alignment, and clean-install test runs. - Use Case: After bumping a package version in package.json, run typecheck and build locally, verify the lockfile is synced, and only then submit the change—reverting immediately if any CI gate fails. ## Quick Start Apply the dependency-ci-contract skill to verify my package.json changes and regenerated lockfile pass typecheck and build before I open a pull request.

Frequently Asked Questions about dependency-ci-contract

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

FAQPage Schema
How do I safely update dependency versions without breaking CI?▼

Update the dependency, regenerate the lockfile, then run typecheck and build locally and confirm both pass before presenting the change for review. If either gate fails, the change is invalid and must be reverted before review.

Why do tests fail after updating package.json dependencies?▼

Test failures after dependency changes are often caused by node_modules being out of sync with the lockfile, not by code defects. Run npm ci or verify lockfile sync before attributing failures to implementation changes.

What should reviewers check for dependency change pull requests?▼

Reviewers should verify that typecheck and build pass after the dependency change and confirm environment consistency before approving any failure attribution. Changes that break CI gates must be reverted before review proceeds.

How do test engineers avoid false failure reports after dependency updates?▼

Confirm the node_modules hash matches the baseline and the TypeScript version matches the project requirement before trusting test results. Run the test suite on a clean install before flagging the implementation as the cause.

When should a dependency change be reverted instead of fixed?▼

Revert immediately when typecheck or build cannot run after the change, since the change is considered invalid at that point. Fix-forward attempts should not be presented for review while CI gates remain broken.