makinari-rol-devops

Verify builds, live deployments, and commit SHAs on GitHub.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-rol-devops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makinari-rol-devops
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-rol-devops
Command: npx skills add https://github.com/Uncodier/API --skill makinari-rol-devops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies builds, ensures deployments are live, confirms the commit SHA exists on GitHub, and finalizes the canonical test_results.json with deployment details before reporting readiness.

Core Features & Use Cases

  • Build verification: verify that the project builds successfully and surface failures for remediation.
  • Preview and deployment validation: ensure the live deployment is reachable and correctly configured, and that deployment artifacts are recorded.
  • Commit provenance verification: check that the HEAD commit exists on GitHub and is linked to the deployment, ensuring traceability.
  • Test results augmentation: extend test_results.json with deployment fields (commit_sha, preview_url_verified) without replacing existing data.
  • Reporting readiness: only mark the release as ready after all checks pass and the gates are satisfied.

Quick Start

Run the DevOps validation step after a merge to extend test_results.json, verify the deployment, and report readiness.

Frequently Asked Questions about makinari-rol-devops

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

FAQPage Schema
How do I gate automated releases with end-to-end DevOps checks?

You can gate automated releases by verifying builds, confirming the deployment is live, and checking the commit SHA exists on GitHub. The validation step reports readiness only after all checks pass and release gates are satisfied.

How do I augment test_results.json with deployment fields without losing existing data?

To augment test_results.json without losing existing data, the DevOps validation extends the file by adding commit_sha and preview_url_verified fields. This preserves your current test data while appending the new deployment details.

How does commit provenance verification work for CI/CD release gates?

Commit provenance verification works by checking that the HEAD commit exists on GitHub and is linked to the deployment. This ensures traceability within your CI/CD pipeline before reporting readiness for the automated release.

Can I validate that a live deployment is reachable before reporting release readiness?

Yes, you can validate that a live deployment is reachable and correctly configured during the DevOps validation step. It confirms the deployment is live and records deployment artifacts before marking the release as ready.

What happens if build verification fails during automated deployment validation?

If build verification fails during automated deployment validation, the process surfaces the build failures for remediation. The release will not be marked as ready until the project builds successfully and all other end-to-end checks pass.

Do I need a GitHub repository to verify commit SHA existence for release gates?

Yes, you need a GitHub repository to verify commit SHA existence. The validation checks that the HEAD commit exists on GitHub to ensure traceability and link the deployment to the correct commit before reporting readiness.