Files
clawhub/.agents/skills/openclaw-design-audit/references/github-pr-delivery.md
T
Patrick Erichsen de29369ba7 feat: adopt shared design system across ClawHub UI (#3026)
* chore: install OpenClaw design system

* feat: adopt shared design system palette

* chore: automate design system updates

* feat: add weekly design system audit

* fix: prevent mobile skills tab overlap

* fix: harden design audit automation

* fix: validate audit changes before execution

* fix: scope design system clone credentials

* fix: align audit with installed design release

* fix: preserve audit artifacts and access

* feat: adopt shared design system on landing page

* fix: align icon geometry with design tokens

* chore: pin design system to v0.0.1

* chore: pin design system to v0.0.1

* chore: pin design system to v0.0.1

* chore: pin design system to v0.0.1

* chore: pin design system to v0.0.1

* fix: migrate ClawHub UI to design tokens

* fix: use public design system installs

* fix: use public design system distribution
2026-07-09 11:05:59 -07:00

2.2 KiB

GitHub Pull Request Delivery

The scheduled ClawHub audit opens a pull request directly against openclaw/clawhub. It does not create or update a tracker issue.

The schedule and credentials live in the consumer repository's GitHub Actions workflow. This design-system skill defines the audit and delivery contract; it does not schedule itself.

Branch And Scope

  • Use a stable automation branch such as automation/design-audit.
  • Start from current remote main.
  • Commit only the report and allowed deterministic fixes.
  • Do not overwrite unrelated human work on an existing branch.

Procedure

  1. Checkout openclaw/clawhub with full history and fetch remote main.
  2. Reset only the dedicated automation branch to origin/main.
  3. Install the design system at the workflow's pinned Git tag.
  4. Run source checks, browser checks, and report generation.
  5. Apply only fixes allowed by fix-policy.md.
  6. Write reports under the consumer's established audit-artifact path.
  7. If the decision table says artifact only, upload the reports and job summary without pushing a branch.
  8. Otherwise commit, force-push the dedicated automation branch with --force-with-lease, then use gh pr create or gh pr edit for the single open pull request owned by that branch.

Pull Request

The title must identify the audit and date. The body includes:

  • design-system version
  • audited ClawHub SHA
  • count by severity
  • commands and routes checked
  • concise expanded findings
  • whether fixes are included
  • paths to JSON, Markdown, and screenshot artifacts

If an open audit pull request exists, update it only when it owns the same stable automation branch. Close it without merge when a later clean run makes its findings obsolete.

Decision Table

Findings Delivery
One or more errors Open or update the pull request
Zero errors and one or more warnings Open or update the pull request
Zero errors, zero warnings, more than five informational findings Open or update the pull request
Zero errors, zero warnings, five or fewer informational findings Artifact and job summary only
No findings Artifact and job summary only; close an obsolete open audit PR