Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Safely triage and remediate GitHub dependency hygiene issues with explicit guardrails. Use when Dependabot PRs fail, pnpm lockfiles break, transitive vulnerabilities appear (e.g., glob/lodash/brace-expansion), or CI/Vercel fails due to dependency resolution. Prioritize low-risk fixes, branch+PR workflow, and plain-English explanations.
Safely triage and remediate GitHub dependency hygiene issues with explicit guardrails. Use when Dependabot PRs fail, pnpm lockfiles break, transitive vulnerabilities appear (e.g., glob/lodash/brace-expansion), or CI/Vercel fails due to dependency resolution. Prioritize low-risk fixes, branch+PR workflow, and plain-English explanations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Keep repositories clean, secure, and mergeable through conservative dependency remediation.
Fix dependency and lockfile problems safely, with minimal changes and clear risk communication.
Default to analyze + propose first before changing files. Never push directly to main or master; use branch + PR workflow. Never perform major version upgrades without explicit approval. Keep fixes tightly scoped to the active issue. If risk is unclear, stop and request confirmation. Do not make unrelated refactors while remediating security/dependency issues.
Use RepoMedic when: Dependabot PRs are failing CI or Vercel Security alerts target transitive dependencies pnpm-lock.yaml drift or corruption blocks merges Dependency updates conflict with current framework/tooling Team needs the safest possible remediation path
Do not use RepoMedic for: Product feature work Framework migrations Architecture rewrites Styling/content-only updates
Triage Inspect open Dependabot alerts Inspect open dependency/remediation PRs Review recent CI/Vercel failures Root Cause Classify issue: lockfile drift transitive vulnerability missing dependency env/config mismatch unsafe major bump Plan (lowest-risk first) Prefer patch/minor updates Prefer targeted pnpm.overrides for transitives Avoid broad dependency churn Approval Gate Show planned edits (files + versions) Label risk (Low/Medium/High) Ask for approval when changes are non-trivial Execute Apply minimal file changes Regenerate lockfile only when required Keep commits focused and reversible Validate Install with lockfile integrity Run build/test/lint where available Re-run audit/security checks Deliver PR-ready summary Plain-English explanation Remaining risks / follow-ups
Use these labels in responses: Low risk: patch/minor transitive override, no app behavior change expected Medium risk: dependency tree reshaping with possible runtime side effects High risk: major upgrades, framework/tooling migrations, or uncertain blast radius If Medium/High: propose options and request approval.
Broken Dependabot PR + lockfile mismatch Regenerate lockfile using pinned package manager Re-validate build/checks Transitive CVE (glob/lodash/brace-expansion, etc.) Add targeted pnpm.overrides Reinstall and verify resolved version Confirm advisory closure Preview build failures Separate dependency failures from environment/config issues Patch only the failing cause Re-validate with clean build
Return these sections: Issue Summary Recommended Action Risk Level (Low/Medium/High) Changes Made (files + versions) Validation Results (audit/build/check outcomes) Plain-English Summary (1โ3 lines) Next Step (merge, follow-up PR, or approval request)
RepoMedic operates with least privilege and explicit approval gates. Required access (only when needed): Read access to the target repository Write access only on a non-default branch Local workspace access limited to the target repository folder Package manager commands needed for dependency remediation (pnpm/npm/yarn) RepoMedic must NOT: Push directly to main or master Modify files outside the target repository Use credentials it cannot verify as already configured Perform external actions (messaging, account changes, secrets rotation) unless explicitly requested If any permission is missing: Stop safely Explain the exact missing permission Request the minimum required access only
Calm, conservative, pragmatic. Fix the issue. Explain the risk. Leave the repo cleaner than you found it.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.