deploy-awid-site

Deploy the reviewed aweb main commit to the awid.ai static site via its landing branch.

82|9|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/awebai/aweb --skill deploy-awid-site-awebai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-awid-site
Source: https://github.com/awebai/aweb/tree/main/.claude/skills/deploy-awid-site
Command: npx skills add https://github.com/awebai/aweb --skill deploy-awid-site-awebai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing the awid.ai static site requires pushing the exact reviewed main commit to a dedicated deploy branch without introducing unreviewed changes, dirty working trees, or non-fast-forward history. This Skill encodes that guarded deployment procedure so the release happens only from a verified state. ## Core Features & Use Cases - Guarded deployment: Runs make deploy-site, which refuses a dirty checkout, requires the commit to match fetched origin/main, enforces a fast-forward from the current deploy-awid-landing tip, and reads the remote ref back after pushing. - Documentation freshness gate: Ensures the site's committed mirrors of docs/identity-guide.md and docs/trust-model.md are current and reviewed before deployment, with make sync-awid-site-docs as the remediation path. - Use Case: After a docs update to the aweb identity guide is reviewed and merged to main, use this Skill to push that exact commit to the deploy-awid-landing branch so Render rebuilds awid.ai, then verify the live site serves the updated content. ## Quick Start Deploy the current reviewed main commit to awid.ai by running the deploy-site make target and then verify the Render deployment and live site content.

Frequently Asked Questions about deploy-awid-site

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

FAQPage Schema
How do I deploy the awid.ai static site from the main branch?

Run `make deploy-site` after the outward production action is authorized. The command builds the site, pushes the exact main SHA to the `deploy-awid-landing` branch, and reads the remote ref back to confirm the push.

How to sync mirrored docs before deploying a static site?

Run `make sync-awid-site-docs` to refresh the site's committed mirrors of `docs/identity-guide.md` and `docs/trust-model.md`. Commit the result, obtain review, and merge it normally before deploying.

Why does make deploy-site refuse to run?

The command refuses a dirty checkout, a commit other than the fetched `origin/main`, or a push that is not a fast-forward from the current `deploy-awid-landing` tip. Clean the working tree and ensure you are on the latest reviewed main commit.

Does the deploy process create commits or release artifacts?

No. The deploy command does not create a commit or participate in artifact release. It only pushes the existing exact main SHA to the landing branch and verifies the remote ref.

How do I verify a Render static site deployment succeeded?

After the `deploy-awid-landing` branch advances, confirm the Render deploy completed, then check that https://awid.ai and both mirrored documents serve the intended content.