Loading…
Repairs a product's main gone red by itself — a dependency audit reading advisories published after the last green run — on a branch off main, and merges it once the suite is green. It runs the audit the product's NFDR names and answers every advisory by the rules development-security uses: an allowed fix (a bump to the fixed release, a renamed identifier, a major bump only with the suite green), an exception for an advisory the product does not reach (in the product's exception record, with a row in the instance upkeep register), and a question for the owner where the only fix is forbidden. It writes a committed report whose first line says merged, unmerged or stopped, or closes with nothing-to-repair when main is not red from its audit. Halts outside a senior-engineer session or the senior-engineer subagent.
dependency-repair is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Dependency Repair ## Purpose A product's `main` can turn red with nobody committing to it: its dependency audit reads advisories published after the last gree. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding dependency-repair to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install eyalgo/kensaiappReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Dependency Repair ## Purpose A product's `main` can turn red with nobody committing to it: its dependency audit reads advisories published after the last green run. This skill re