scan-astro

Detect CSP violations, frontmatter issues, and hydration anomalies in Astro projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TrevorPLam/agency --skill scan-astro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-astro
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/scan-astro
Command: npx skills add https://github.com/TrevorPLam/agency --skill scan-astro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Astro projects often suffer from CSP violations, frontmatter inconsistencies, and hydration pattern issues that can degrade security and user experience. This skill automates detection and reporting for these problems across the monorepo.

Core Features & Use Cases

  • CSP validation for Astro applications to ensure inline scripts and styles are compliant with security policies.
  • Frontmatter linting to catch missing or malformed frontmatter blocks, incorrect metadata, and syntax issues in .astro files.
  • Hydration pattern checks to identify hydration-related antipatterns and rendering pitfalls in Astro components.
  • Scope: apps/agency-web/ and any .astro files in the monorepo, enabling pre-deployment quality checks.

Quick Start

Run the Astro scan commands in Windsurf to detect CSP, frontmatter, and hydration issues in apps/agency-web and relevant .astro files.

Frequently Asked Questions about scan-astro

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

FAQPage Schema
How do I detect CSP violations in Astro projects before deployment?

You can detect Astro CSP violations by running an automated scan that validates inline scripts and styles against security policies. This skill checks .astro files within apps/agency-web and across the monorepo to surface compliance issues pre-deployment.

What is the best way to lint frontmatter in .astro files across a monorepo?

Linting frontmatter in .astro files involves checking for missing or malformed blocks and incorrect metadata syntax. This skill automates that validation across the monorepo, deduplicating generated issues to streamline pre-deployment quality checks.

How do I identify hydration pattern anomalies in Astro components?

Identifying hydration anomalies requires checking Astro components for rendering pitfalls and antipatterns. This skill uses custom checks alongside Astro tooling to validate hydration patterns, targeting .astro files in apps/agency-web and the wider monorepo.

Does this Astro issue scanner work without external dependencies?

Yes, the Astro issue scanner operates without external dependencies, relying entirely on built-in Astro tooling and custom checks. It validates security, metadata, and rendering patterns within a 30-second execution limit.

What are the limitations when scanning Astro projects for security and rendering issues?

The primary limitation is a strict 30-second execution limit for the scanning process. Additionally, the scope is restricted to .astro files in apps/agency-web and the surrounding monorepo, meaning projects outside this structure are not validated.

Why does my Astro frontmatter metadata fail pre-deployment quality checks?

Astro frontmatter metadata fails quality checks due to missing blocks, malformed syntax, or incorrect metadata formatting. This skill automates the detection of these specific inconsistencies in .astro files before deployment.