Aggregate cross-repo pipeline statuses into a read-only board.
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill get-status
Please help me install this Agent Skill. Skill: Get Status Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/get-status Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill get-status
Cross-repo visibility into pipeline status across multiple repos, providing a single pane to monitor backlog, in-progress work, shipped today, and bottlenecks without mutating any data.
Request a fresh, read-only cross-repo status board update across all tracked repos.
High-intent search queries and answers about installing and using this skill.
You can monitor cross-repo pipeline statuses by aggregating data from multiple repositories into a single, read-only board. This consolidates backlog, in-progress work, and shipped items into one view without mutating any source data.
A read-only status board is a non-mutating aggregation layer that pulls pipeline data from multiple sources. It categorizes items into BACKLOG, IN PROGRESS, and SHIPPED TODAY while strictly enforcing non-mutating behavior to ensure source data remains untouched.
Yes, you can detect CI blockers, stalled dispatches, and queue congestion across multiple repositories. The aggregated board surfaces these specific bottlenecks to help engineering ops teams identify risk and throughput issues across teams.
To generate a cross-repo status board update, you simply request a fresh, read-only board update across all tracked repositories. The skill handles parallel data pulls, deduplication, and categorization automatically.
Yes, the cross-repo pipeline board supports parallel data pulls from up to six sources. It performs deduplication on the pulled data to ensure the final aggregated board remains accurate and free of duplicate entries.
The primary limitation of a read-only board is its strict non-mutating behavior; it cannot modify, update, or transition any pipeline states. It is designed exclusively for viewing statuses and surfacing bottlenecks rather than executing workflow actions.
rittmananalyticsManage Fivetran data pipeline connections via API calls.
webrix-aiConfigure incident alerting workflows with Slack and Grafana integrations.
isukharevBuild a read-only Jira sprint dashboard using the atl CLI.
adaptive-enforcement-labAggregate Kyverno policies from multiple teams into a unified OCI image.
