تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

dependency-ci-contract

النجوم٠

التفرعات٠

آخر تحديث٨ يوليو ٢٠٢٦ في ١٠:٥٦

Keep dependency and lockfile changes aligned with CI expectations.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

ZaxbyHub

ZaxbyHub/ragappv3

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	dependency-ci-contract
description	Keep dependency and lockfile changes aligned with CI expectations.
generated_from_knowledge	["f178f314-bce2-474b-bb4f-091d6662b5f7","d38f4988-551c-4d4d-b4b2-be6dc0d75c30"]
source_knowledge_ids	["f178f314-bce2-474b-bb4f-091d6662b5f7","d38f4988-551c-4d4d-b4b2-be6dc0d75c30"]
generated_at	"2026-07-08T07:30:00.000Z"
confidence	0.6
status	active
version	1
skill_origin	generated

Dependency and CI Contract

Trigger

Changing dependency versions
Updating package.json
Regenerating lockfiles
Investigating test/build failures after dependency changes

Required Procedure

Run typecheck and build locally and confirm they pass before presenting code for review.
Verify node_modules matches the lockfile before reporting test failures.
Re-run failed CI gates after dependency sync before escalating.

Forbidden Shortcuts

Change dependency versions that cause typecheck or build to fail.
Report test failures as code defects before confirming the environment matches the lockfile baseline.

Delegation Template

When delegating a task affected by this skill, include:

SKILLS: file:.opencode/skills/generated/dependency-ci-contract/SKILL.md

Reviewer Checks

Verify typecheck and build pass after dependency changes.
Verify environment consistency before approving failure attribution.

Test Engineer Checks

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

Source Knowledge IDs

f178f314-bce2-474b-bb4f-091d6662b5f7 — Dependency version changes must not break CI gates. If typecheck or build cannot run after a change, the change is invalid and must be reverted before review.
d38f4988-551c-4d4d-b4b2-be6dc0d75c30 — Run npm ci or verify lockfile sync before attributing test/build failures to code changes; missing dependencies produce spurious failures that waste review cycles.

المزيد من هذا المستودع

نفس المستودع

qa-sweep

ZaxbyHub/ragappv3

Apply when implementing features, fixing bugs, debugging errors, investigating failures, tracing root causes, reviewing tech debt, tracing issues, planning fixes, or completing any task. Enforces parallel sub-agent implementation, independent adversarial review, and a 95% confidence gate before stopping.

2026-07-100

writing-tests

ZaxbyHub/ragappv3

RAGAPPv3 testing policy and conventions. Load before writing or modifying any test, fixing a test/CI failure, or adding coverage. Covers backend pytest + unittest (SimpleConnectionPool dependency-override harness, FK cascades, the Python 3.11-vs-local event-loop trap) and frontend Vitest + React Testing Library + jsdom (MemoryRouter, Radix Select, react-virtual mock patterns). This repo's frontend uses Vitest, NOT bun:test.

2026-07-100

qa-gate-disciplined-completion

ZaxbyHub/ragappv3

Verify all required QA gate artifacts and completion criteria before marking a task or phase complete.

2026-07-080

testing-mock-async-hygiene

ZaxbyHub/ragappv3

Keep mocks, async setup, and test assertions clean and aligned with the code under test.

2026-07-080

ci-compatibility-audit

ZaxbyHub/ragappv3

Lightweight PR-time audit for whether changes are compatible with the actual RAGAPPv3 GitHub Actions workflow, dependency lockfiles, scripts, and cross-platform local validation.

2026-07-060

reviewing-code-core

ZaxbyHub/ragappv3

Evidence-first code review for correctness bugs, AI-generated code smells, unsupported claims, unwired functionality, dependency hallucinations, and release-to-code mismatches.

2026-07-060

name	dependency-ci-contract
description	Keep dependency and lockfile changes aligned with CI expectations.
generated_from_knowledge	["f178f314-bce2-474b-bb4f-091d6662b5f7","d38f4988-551c-4d4d-b4b2-be6dc0d75c30"]
source_knowledge_ids	["f178f314-bce2-474b-bb4f-091d6662b5f7","d38f4988-551c-4d4d-b4b2-be6dc0d75c30"]
generated_at	"2026-07-08T07:30:00.000Z"
confidence	0.6
status	active
version	1
skill_origin	generated

Dependency and CI Contract

Trigger

Changing dependency versions
Updating package.json
Regenerating lockfiles
Investigating test/build failures after dependency changes

Required Procedure

Run typecheck and build locally and confirm they pass before presenting code for review.
Verify node_modules matches the lockfile before reporting test failures.
Re-run failed CI gates after dependency sync before escalating.

Forbidden Shortcuts

Change dependency versions that cause typecheck or build to fail.
Report test failures as code defects before confirming the environment matches the lockfile baseline.

Delegation Template

When delegating a task affected by this skill, include:

SKILLS: file:.opencode/skills/generated/dependency-ci-contract/SKILL.md

Reviewer Checks

Verify typecheck and build pass after dependency changes.
Verify environment consistency before approving failure attribution.

Test Engineer Checks

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

Source Knowledge IDs

f178f314-bce2-474b-bb4f-091d6662b5f7 — Dependency version changes must not break CI gates. If typecheck or build cannot run after a change, the change is invalid and must be reverted before review.
d38f4988-551c-4d4d-b4b2-be6dc0d75c30 — Run npm ci or verify lockfile sync before attributing test/build failures to code changes; missing dependencies produce spurious failures that waste review cycles.