local-attest

Run local CI matrices and gate remote GitHub Actions via SHA-pinned attestation comments.

Updated Apr 14, 2026

Search Tags:#testing #devops #github-actions #pull-request #local-ci #ci-optimization #ci-attestation

Ready to run

npx skills add https://github.com/kaiohenricunha/dotbabel --skill local-attest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: local-attest
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/local-attest
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill local-attest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Running the same CI matrix on remote GitHub Actions runners after local verification of changes wastes runner minutes and slows down pull request feedback loops for the entire team.

Core Features & Use Cases

Local CI Matrix Execution: Run your project's full configured CI test matrix on your local machine to validate changes before pushing.
SHA-Pinned Attestation Gating: Post a hidden, SHA-pinned PR comment from a trusted user to gate remote CI jobs, causing them to skip entirely for that exact commit.
Use Case: For maintainers who have already run all tests locally, this skill eliminates duplicate remote test runs, cutting CI costs and reducing wait times for PR checks without weakening pipeline security.

Quick Start

Use the local-attest skill to run your project's CI matrix locally and post an attestation comment to skip redundant remote CI runs for the current pull request.

Frequently Asked Questions about local-attest

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

FAQPage Schema

How do I skip redundant GitHub Actions CI runs after testing locally?▼

To skip redundant GitHub Actions CI runs after local verification, you can post a SHA-pinned pull request attestation comment from a trusted user. This gates remote CI jobs and causes them to skip entirely for that exact commit without weakening pipeline security.

What is CI attestation gating for pull requests?▼

CI attestation gating for pull requests is a mechanism that uses a hidden, SHA-pinned PR comment from a trusted user to gate remote CI jobs. It allows maintainers to skip duplicate remote test execution on GitHub Actions runners after verifying code changes locally.

Can I use local CI execution to save GitHub Actions runner minutes for maintainers?▼

Yes, you can use local CI matrix execution to validate changes on your local machine before pushing. By posting a SHA-pinned attestation comment, maintainers can skip redundant remote CI runs, saving runner minutes and reducing pull request feedback wait times.

How do I gate remote CI jobs with a SHA-pinned PR comment?▼

You can gate remote CI jobs by posting a hidden, SHA-pinned PR comment from a trusted user account after running your project's full configured CI test matrix locally. This causes the remote GitHub Actions workflow gates to skip duplicate test execution for that exact commit.

Does skipping remote CI runs weaken pipeline security for GitHub Actions workflows?▼

Skipping remote CI runs does not weaken pipeline security when using SHA-pinned PR attestation comments from trusted users. The attestation gates remote CI jobs by binding the skip condition to an exact commit SHA, ensuring only verified local changes bypass remote test execution.

What are the limitations of using attestation comments to skip GitHub Actions CI?▼

The limitation of using attestation comments to skip GitHub Actions CI is that it applies specifically to maintainer pull request validation workflows in repositories with configured CI matrices and GitHub Actions workflow gates, requiring a trusted user to post the SHA-pinned comment.