skills.rest
BedaBeda-Growth
BedaBeda-GrowthOFFICIAL
Explore all skills by this author →
GitHub

ci-full-verify

Coordinate ci-verify workflows across repositories and trigger Playwright matrix runs.

Updated Feb 3, 2026
Search Tags:#automation#playwright#github-actions#cross-repo#workflow-dispatch#ci-verification
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill ci-full-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-full-verify
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/ci-full-verify
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill ci-full-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Centralizes cross-repo CI verification to ensure consistent validation across multiple projects, reducing manual coordination and drift.

Core Features & Use Cases

  • Cross-repo orchestration of ci-verify workflows across Rocket, App, Spark, scceo, and other targets.
  • Merges ci-integration branches into ci-testing-verify and triggers GitHub Actions for a full Playwright matrix against CI_TESTING_URL.
  • Reads and respects each repo's own ci-verify skill before dispatching to ensure governance and safety.

Quick Start

Dispatch Jules to run the per-repo ci-verify workflow across all target repositories.

Frequently Asked Questions about ci-full-verify

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

FAQPage Schema
How do I orchestrate cross-repo CI verification across multiple repositories?▼

You orchestrate cross-repo CI verification by dispatching per-repo ci-verify workflows, merging ci-integration branches into ci-testing-verify, and triggering GitHub Actions for the full Playwright matrix against CI_TESTING_URL.

Can I trigger a full Playwright matrix across multiple repositories using GitHub Actions?▼

Yes, triggering a full Playwright matrix across repositories involves coordinating session dispatches, merging ci-integration branches, and executing the matrix against CI_TESTING_URL via GitHub Actions.

What is the best way to centralize CI verification to prevent configuration drift across projects?▼

Centralizing CI verification prevents drift by reading and respecting each repository's own ci-verify skill before dispatching, ensuring consistent validation and governance across all target projects.

Does cross-repo workflow dispatch require ci-integration branches to exist before running?▼

Yes, cross-repo workflow dispatch verifies that ci-integration branches exist before merging them into ci-testing-verify and triggering the full Playwright matrix via GitHub Actions.

How do I monitor results and sync ledgers for automated cross-repo CI workflows?▼

You monitor results and sync ledgers by coordinating session dispatches across target repositories, which enforces deterministic scripts and manages result monitoring and ledger syncing.

Do I need per-repo ci-verify workflows configured before dispatching cross-repo CI orchestration?▼

Yes, per-repo ci-verify workflows must be configured, as the orchestration reads and respects each repository's own ci-verify skill before dispatching to ensure proper governance and safety.

Related Skills

Explore More Software Engineering Skills→
jfrogjfrog
5

jfrog-oidc-setup

Configure OpenID Connect integration between GitHub Actions and JFrog Platform.

Official
Advanced
zhangzhang-111-izhangzhang-111-i
2

report

Generate Markdown and HTML test reports from Playwright JSON results.

Community
Advanced
felipeganamefelipeganame
2

github-workflow-automation

Automate GitHub Actions workflows for CI/CD pipeline optimization.

Community
Advanced
Aktoh-CyberAktoh-Cyber

github-release-management

Automate GitHub release orchestration across multiple repositories with semantic versioning.

Official
Advanced