crowi-deps

Resolves GitHub Dependabot security alerts by bumping dependencies and validating with pnpm.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-deps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-deps
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-deps
Command: npx skills add https://github.com/crowi/crowi --skill crowi-deps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open Dependabot security alerts pile up in a pnpm monorepo, and fixing them properly requires distinguishing direct from transitive dependencies, choosing between version bumps and pnpm overrides, and verifying nothing breaks. This Skill automates that entire remediation workflow for the Crowi repository.

Core Features & Use Cases

  • Alert triage and classification: Fetches open Dependabot alerts via the GitHub CLI, then classifies each package as direct or transitive using package.json grep and pnpm why.
  • Root-cause remediation: Bumps direct dependencies, upgrades parent packages for transitive ones, and applies per-major pnpm.overrides only when no bump path exists; defers major-upgrade-only fixes to a report.
  • Override housekeeping: Audits existing pnpm.overrides entries one by one and removes those no longer needed because parent packages now resolve patched versions.
  • Verified commits: Runs pnpm install, lint, type-check, and affected package tests before committing (never pushes without user instruction).
  • Use Case: Run /crowi-deps when you notice dependency maintenance has slipped; the Skill resolves all open security alerts, cleans stale overrides, and leaves verified commits ready for review.

Quick Start

Ask the assistant to run the crowi-deps skill to fetch open Dependabot alerts, fix them with version bumps or overrides, verify with lint and tests, and commit the results.

Frequently Asked Questions about crowi-deps

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

FAQPage Schema
How do I fix Dependabot security alerts in a pnpm monorepo?

Fetch open alerts with the GitHub CLI, classify each package as direct or transitive, then bump direct dependencies or upgrade parent packages for transitive ones. Verify with pnpm install, lint, type-check, and tests before committing.

When should I use pnpm overrides for security vulnerabilities?

Use pnpm overrides only for genuinely transitive dependencies whose parent package cannot be upgraded to pull a patched version. Write them per-major, like "undici@6": "^6.27.0", and record the reason in the commit message.

How do I remove stale pnpm overrides that are no longer needed?

Remove one override entry at a time, run pnpm install, then check pnpm why to confirm all resolved versions stay at or above the pinned version. If they do, the parent now resolves the patched version naturally and the override can be deleted.

What happens when a security fix requires a major version upgrade?

The Skill does not force major upgrades. It records the alert as pending in the report with its blocker, and a spec should be created if work is approved; pnpm outdated and Dependabot can re-derive the remaining items anytime.

Does this workflow push commits to the remote repository?

No. The workflow stops at local commits after verification passes with zero lint errors, type-check, and affected package tests. Pushing waits for explicit user instruction.