whats-behind
This skill should be used when the user asks "what's behind", "what needs a bump", "what's out of date across our repos", "which products are lagging", "who's on an old version", "portfolio dependency audit", "audit our dependencies across products", "are any products falling behind", "version drift", "which repos have stale actions", "keep the runners updated", or wants a cross-repo currency check spanning EVERY repo in a portfolio rather than one repository. Compares each repo's pinned GitHub Actions, toolchain versions, runner labels, and Dependabot coverage against its peers, then reports which repos are lagging and whether the cause is a missing automation config. Read-only — never edits pins, never opens PRs. For things that are broken or stalled rather than merely old, use whats-on-fire; for single-repo prioritization, use that repository's own survey-work skill.
Target: Software development & testing. Automatically collected · unverified.
Use with Claude Desktop
A guide for this combination is not available yet, and compatibility has not been verified.
Requirements
- Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.
Choose an AI tool with documented instructions, or save the resource and request a guide after the page loads.
Read the author’s documentation ↗