一键在 Manus 中运行任何 Skill

validate-and-repair

星标0

分支0

更新时间2026年4月6日 20:33

Validate generated Astro.js code and apply auto-fixes for common errors. Run static checks (astro check, tsc, build) and repair known error patterns. Use this skill when you need to validate generated code, fix build errors, or repair common Astro/Shadcn integration issues. Always use this skill after code generation, when tests fail, or when the user mentions "validation", "fix errors", "repair code", or "build failed".

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

AtomiCloud

AtomiCloud/cyanate.mercury

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Validate and Repair

Validate generated Astro.js code and apply auto-fixes for common errors. Outputs validation reports and applies surgical fixes.

When to use this skill

Use this skill when you need to:

Run static validation on generated Astro code
Fix build errors
Apply auto-fixes for known error patterns
Verify code quality before deployment

Your task

Run validation checks on the Astro project
Generate validation report as validation-report.json
Apply auto-fixes for repairable errors
Re-run validation to verify fixes

Validation checks

Run these commands in order:

# 1. Astro syntax check
bunx astro check

# 2. TypeScript check
bun run typecheck

# 3. Build test
bun run build

Output format

Save as validation-report.json:

{
  "files": [
    {
      "file": "src/pages/index.astro",
      "passed": true,
      "violations": []
    },
    {
      "file": "src/components/Header.astro",
      "passed": false,
      "violations": [
        {
          "rule": "missing-layout-import",
          "severity": "error",
          "line": 1,
          "message": "Page must import Layout",
          "autoFixable": true
        }
      ]
    }
  ]
}

Auto-fixable violations

See references/common-errors.md for the full list of auto-fixable patterns.

Validation rules to check

For ALL `.astro` files:

File parses as valid Astro (frontmatter fences present)
No {tokens., ${theme., {colors. patterns (unreplaced tokens)
No inline style="..." with raw colors
No bg-[#...], text-[#...] arbitrary Tailwind colors
No <html>, <head>, <body> in component files (only in Layout)
All imports use @/ path alias for ui/lib

For page files (`src/pages/*.astro`):

Imports Layout component
Wraps content in <Layout>...</Layout>
Has valid frontmatter

For Shadcn component usage:

Imports from @/components/ui/[name]
Interactive components have client:load or client:visible
cn() imported from @/lib/utils when used

For `globals.css`:

Required imports present
@theme inline block with color mappings
CSS variables defined in :root
Values in OKLCH format

Build check

astro build completes without errors
No TypeScript errors
All assets generated correctly

Important notes

Read common-errors.md before applying fixes
Apply fixes surgically - only change what's broken
Re-run validation after each fix
Report which files were modified
Use Edit tool for precise changes

Exit codes

If all checks pass: Output "✅ VALIDATION_PASSED"
If errors found: Output validation report and apply auto-fixes
If auto-fixes fail: Flag for manual review

同仓库更多 Skills

同仓库

astro-codegen

AtomiCloud/cyanate.mercury

Generate Astro.js code (layouts, components, pages) from design briefs using Shadcn UI components. Use this skill when you need to create .astro files from a design-brief.json specification. Works with Shadcn Skill for component APIs, Frontend Design Skill for visual polish, and Astro AI Docs for best practices. Always use this skill when generating Astro code, creating .astro files, or implementing page layouts. The skill includes reference files for layout-specific, component-specific, and page-specific generation rules.

2026-04-070

design-brief

AtomiCloud/cyanate.mercury

Generate a comprehensive design brief for Astro.js website generation from scraper output and design tokens. Use this skill when you have scraped website data (structure.json, schema.json, content.json) and design tokens, and need to create a section-by-section blueprint for each page. Works with Shadcn Skill to understand available components and composition patterns. Always use this skill when the user mentions "design brief", "site blueprint", "page planning", "component mapping", or needs to bridge scraped content to code generation.

2026-04-070

extract-design-tokens

AtomiCloud/cyanate.mercury

Extract design tokens (colors, typography, spacing, borders, shadows) from a reference website using headless browser automation. Use this skill when you need to scrape a website's visual design values and convert them to OKLCH format for Shadcn theming. Works with Webapp Testing Skill for Playwright automation and Shadcn Skill for CSS variable mapping. Always use this skill when the user mentions "extract design", "scrape styles", "get colors from website", "design tokens", or wants to clone/mimic a site's visual design.

2026-04-070

iterate-and-fix

AtomiCloud/cyanate.mercury

Iteratively fix specific failing files based on validation errors or quality feedback. Perform targeted re-generation of individual files with error context injected. Use this skill when validation fails, quality scores are too low, or specific files need re-generation. Always use this skill after validate-and-repair or test-and-quality when errors persist, or when the user mentions "fix this file", "re-generate", "iterate", or needs to address specific feedback.

2026-04-070

shadcn

AtomiCloud/cyanate.mercury

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

2026-04-070

test-and-quality

AtomiCloud/cyanate.mercury

Run functional and visual quality tests on generated Astro.js websites. Start dev server, visit pages, check for errors, and evaluate visual quality using automated heuristic checks. Use Webapp Testing Skill for Playwright automation. Always use this skill after code generation, when user mentions "testing", "quality check", "visual review", or needs to verify the generated site works correctly.

2026-04-070

name

validate-and-repair

description

Validate and Repair

Validate generated Astro.js code and apply auto-fixes for common errors. Outputs validation reports and applies surgical fixes.

When to use this skill

Use this skill when you need to:

Run static validation on generated Astro code
Fix build errors
Apply auto-fixes for known error patterns
Verify code quality before deployment

Your task

Run validation checks on the Astro project
Generate validation report as validation-report.json
Apply auto-fixes for repairable errors
Re-run validation to verify fixes

Validation checks

Run these commands in order:

# 1. Astro syntax check
bunx astro check

# 2. TypeScript check
bun run typecheck

# 3. Build test
bun run build

Output format

Save as validation-report.json:

{
  "files": [
    {
      "file": "src/pages/index.astro",
      "passed": true,
      "violations": []
    },
    {
      "file": "src/components/Header.astro",
      "passed": false,
      "violations": [
        {
          "rule": "missing-layout-import",
          "severity": "error",
          "line": 1,
          "message": "Page must import Layout",
          "autoFixable": true
        }
      ]
    }
  ]
}

Auto-fixable violations

See references/common-errors.md for the full list of auto-fixable patterns.

Validation rules to check

For ALL `.astro` files:

File parses as valid Astro (frontmatter fences present)
No {tokens., ${theme., {colors. patterns (unreplaced tokens)
No inline style="..." with raw colors
No bg-[#...], text-[#...] arbitrary Tailwind colors
No <html>, <head>, <body> in component files (only in Layout)
All imports use @/ path alias for ui/lib

For page files (`src/pages/*.astro`):

Imports Layout component
Wraps content in <Layout>...</Layout>
Has valid frontmatter

For Shadcn component usage:

Imports from @/components/ui/[name]
Interactive components have client:load or client:visible
cn() imported from @/lib/utils when used

For `globals.css`:

Required imports present
@theme inline block with color mappings
CSS variables defined in :root
Values in OKLCH format

Build check

astro build completes without errors
No TypeScript errors
All assets generated correctly

Important notes

Read common-errors.md before applying fixes
Apply fixes surgically - only change what's broken
Re-run validation after each fix
Report which files were modified
Use Edit tool for precise changes

Exit codes

If all checks pass: Output "✅ VALIDATION_PASSED"
If errors found: Output validation report and apply auto-fixes
If auto-fixes fail: Flag for manual review

validate-and-repair

Validate and Repair

When to use this skill

Your task

Validation checks

Output format

Auto-fixable violations

Validation rules to check

For ALL .astro files:

For page files (src/pages/*.astro):

For Shadcn component usage:

For globals.css:

Build check

Important notes

Exit codes

同仓库更多 Skills

同仓库更多 Skills

Validate and Repair

When to use this skill

Your task

Validation checks

Output format

Auto-fixable violations

Validation rules to check

For ALL .astro files:

For page files (src/pages/*.astro):

For Shadcn component usage:

For globals.css:

Build check

Important notes

Exit codes

For ALL `.astro` files:

For page files (`src/pages/*.astro`):

For `globals.css`:

For ALL `.astro` files:

For page files (`src/pages/*.astro`):

For `globals.css`: