whats-behind

Audits pinned GitHub Actions, toolchains, and Dependabot coverage across every repo in a portfolio.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill whats-behind-sassy-dog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: whats-behind
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/whats-behind
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill whats-behind-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) components.

What problem does it solve? Repos in a portfolio silently drift apart on shared versions — one repo sits three majors behind on actions/checkout while its siblings moved on, and nothing fails loudly to reveal it. This skill runs a read-only, peer-relative currency audit across every repo and, crucially, reports why each laggard is behind (usually a missing Dependabot config) rather than just listing stale pins. ## Core Features & Use Cases - Cross-repo drift scan: A Bash script walks local checkouts and emits JSON covering pinned GitHub Actions versions, toolchain pins, hosted vs self-hosted runner counts, and Dependabot coverage per repo. - Peer-relative ranking: Compares each repo against the portfolio mode (not upstream registries), tiering findings as internally inconsistent, major-gap, or minor-gap laggards. - Cause classification: Cross-references every laggard against Dependabot config to distinguish unmanaged repos (prescribe rendering config) from managed-but-stalled ones. - Use Case: Ask "which of our products are falling behind on dependency versions?" and get a markdown report ranking laggards, flagging repos with no automation watching them, and recommending fixes in priority order. ## Quick Start Ask the agent to run a what's-behind audit across the portfolio to find which repos are lagging their peers on GitHub Actions and toolchain versions.

Frequently Asked Questions about whats-behind

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

FAQPage Schema
How do I audit dependency versions across multiple GitHub repos?

Run the pull-version-drift.sh script with PORTFOLIO_ROOT pointing at your repo checkouts. It scans each repo's workflow files for pinned actions and toolchain versions, then emits JSON you rank against the portfolio mode to find laggards.

How to find which repos are missing Dependabot configuration?

The drift script checks each repo for .github/dependabot.yml and whether it covers the github-actions ecosystem, reporting coverage per repo. Repos without config are flagged as unmanaged, since their pins will drift again after any manual bump.

Does this work without network access or the GitHub CLI?

The core comparison is peer-relative and runs entirely on local checkouts, so it works offline. The gh CLI is only needed to exclude archived repos; without it, the GitHub MCP list-repos capability provides the same roster.

Will this tool update outdated GitHub Actions versions automatically?

No, the audit is strictly read-only — it never edits pins, writes Dependabot configs, or opens PRs. It reports findings and prescribes fixes, leaving the actual changes to humans or a setup-deps style generator.

Why rank repos against peers instead of the latest upstream release?

Peer-relative ranking uses the portfolio mode as the standard, so one early adopter does not flag everyone else as behind. It also works offline and only surfaces versions the fleet has actually converged on.