release-check

$npx mdskill add langchain-ai/design-agent/release-check

Stop at the first failure and report it; do not tag or publish. Tagging and publishing are the maintainers' call.

SKILL.md

.github/skills/release-checkView on GitHub ↗
---
name: release-check
description: Run the release gates before tagging a Design Agent release: hygiene, secrets, licenses, docs, tests, and the human reviews.
---

# Release check

Stop at the first failure and report it; do not tag or publish. Tagging and publishing are the
maintainers' call.

1. `uv sync --all-extras --dev`, `uv run ruff check .`, `uv run ruff format --check .`,
   `uv run mypy src`, `uv run pytest -q`, `uv run pytest -q -m render` (Docker), `uv run design-agent
   demo`, `uv run design-agent skills verify`.
2. `DESIGN_AGENT_RELEASE_CHECK=1 uv run pytest -q tests/unit/test_public_hygiene.py`: no internal
   identifiers, licensed fonts, third-party media or build notes; the pre-release paths
   (`docs/prep/`, `IMPLEMENTATION_PROMPT.md`, `scripts/import_from_reference.py`) are deleted first.
3. `gitleaks detect --no-banner` (config `.gitleaks.toml`) on the full history.
4. Licenses: `fonts/LICENSES.md` matches `fonts/`, `licenses/` covers every vendored or bundled
   component, `NOTICE.md` is current, and `skills-lock.json` names each upstream license.
5. Docs: every link resolves (`uv run pytest -q tests/unit/test_docs_links.py`), README quick start
   works from a clean clone, `CHANGELOG.md` has the release.
6. `uv run mda build` from a clean checkout; inspect `.mda/build` and `.mda/__contexthub__`.
7. Human gates (SPEC §24): partner reviews (HyperFrames, Paper), legal review, sample-brand and
   gallery review. Record who signed off outside the repository.

More from langchain-ai/design-agent

SkillDescription
brand-onboardingBuild the active brand pack in workspace/brand/ from a brand guide, website, files or a Paper file, validate it, and have a person review it.
data-vizCharts, stat cards, flywheels and diagrams (flows, architectures, hierarchies) rendered on brand from a JSON spec to PNG and SVG. Use for any visual whose job is numbers or relationships, including restyling an attached chart or diagram.
design-agent-customizeChange what Design Agent knows and does. Teach it a new deliverable with a runtime skill, change its instructions, design doctrine or checks, connect MCP servers and tools, or change models and cost caps. Use when someone wants it to make something new, follow a new rule, or use another tool.
design-agent-deployPut Design Agent in a team's Slack. Deploy it to Managed Deep Agents (one command, managed Slack app) or self-host it with Docker Compose, verify it with a real request, ship updates, and keep a separate test copy. Use when someone wants the agent running for their team.
design-agent-evalsFind out whether a change made Design Agent better or worse. Run the eval set or a few tasks before and after against the same model, read the reports, look at the files, and turn a real request that went wrong into a task. Use after changing instructions, skills, checks or models, or when someone asks how good it is.
design-agent-onboardingInstall and configure Design Agent, add a brand, connect Paper, choose MDA or self-hosting, and diagnose setup without exposing credentials.
design-agent-troubleshootDiagnose Design Agent when something fails. Setup, a render, a deploy, Slack or a model call. Run doctor and the connection tests, read logs and traces, match the symptom to its fix, and never print credentials. Use when a command errors, a reply never comes, or a file looks wrong.
design-agent-updateBring a fork or clone of Design Agent up to date with the upstream repository while keeping the team's brand, skills and edits, rebuild what changed, and redeploy safely. Use when someone asks to update, upgrade or pull the latest Design Agent.
design-wikiDesign doctrine to weigh on any visual. Hierarchy, typography, colour, layout, platform sizes, chart and diagram principles, and the review rubric critics score against.
embedded-captions>