withastro

Cut a new rosie release. Use when asked to publish a release, bump the version, or ship X.Y.Z. Covers the version bump, the tag that triggers CI, and what gets published (GitHub release, npm, Homebrew, AUR, Debian, FreeBSD).

Fixture skill standing in for cloudflare/skills' Pages skill in the wrangler integration test

Fixture skill standing in for cloudflare/skills' Workers skill in the wrangler integration test

A test skill used by rosie's regression suite

A skill with invisible chars and comments. Used to test sanitize_skill.

A skill the package actually authors and ships

Represents a consumer-installed third-party skill that the project happened to commit. rosie must not treat these as the package's own skills when this repo is being installed.

First skill in the multi-skills test fixture

Use when building, debugging, reviewing, or documenting Flue agents, workflows, channels, skills, tools, sandboxes, targets, routing, persistence, observability, or CLI usage; routes coding agents to version-matched Flue documentation through the CLI.

Compact the current conversation into a handoff document for another agent to pick up.

Research, implement, review, and validate one first-party Flue HTTP channel across its package, example, channel blueprint, documentation, Node runtime, Cloudflare Workers runtime, and publish artifact. Use when adding a provider channel, expanding an existing channel's verified HTTP surface, auditing channel conformance, or evaluating whether a provider is eligible for the stateless webhook model.

Flue documentation editor. Use when reorganizing, rewriting, reviewing, or approving docs pages and navigation; turns rough or AI-generated documentation into scoped, accurate, human-editorialized content through a collaborative outline-and-draft workflow informed by Diátaxis.

Release public npm packages from this repository. Use ONLY when the user explicitly asks to release and supplies patch, minor, major, or an explicit version number.

Reviews an answer using packaged supporting guidance.

Creates and rewrites Flue API reference documentation from package-visible TypeScript exports and audited source-adjacent JSDoc. Use when authoring concise reference pages under apps/docs/src/content/docs/api/ or reference pages such as reference/configuration.md. Do not use for narrative guides, tutorials, or automated maintenance checks.

Generate a personalized greeting for a given name. Use when asked to greet someone.

Triage a bug report. Reproduces the bug, diagnoses the root cause, verifies whether the behavior is intentional, and attempts a fix. Use when asked to "triage issue

Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.

Handle main-to-next merge tasks including conflict resolution, changeset cleanup, and CI fix-ups. Use when merging main into next.

Create a changeset for the Astro monorepo. Use this skill whenever you need to add a changeset file to a PR, write a changelog entry, or document a package version bump. Also trigger when the user says "add a changeset", "write a changeset", "create a changeset", or when another skill instructs you to create a changeset.

Write and update Astro pull requests with reviewer-friendly titles and high-signal bodies. Trigger whenever the user asks to create a PR, open a PR, draft a PR, update PR title/body, or write PR notes/summary/description.

Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements. Use when asked to "analyze workflow logs", "review action runs", or "analyze GitHub Actions".

Manage Astro minor releases end-to-end — from creating GitHub milestones and Linear tickets to executing release-day tasks like Algolia indexing and merging articles. Use this skill whenever the user mentions setting up an Astro release, creating release tickets, preparing a minor release, "release day", running the Astro release checklist, indexing Algolia after a release, or anything related to the Astro release process. Also trigger for phrases like "set up 6.4 release", "create the release milestone", "release day for Astro", or "time to ship".

Review and assess security advisories filed against the Astro framework. Use this skill whenever someone asks to review a security advisory, triage a GHSA, evaluate a vulnerability report, assess a CVE, or look at a security disclosure for Astro. Also trigger when the user shares a security advisory and asks whether it's valid, real, exploitable, or worth fixing — even if they don't use the word "security" explicitly but paste something that looks like a vulnerability report with a PoC or GHSA identifier.

Trigger and monitor a preview release for an Astro pull request. Use this skill whenever the user wants to publish a preview/canary build of an Astro PR so that reporters or users can test a fix before it merges — including phrases like "create a preview release", "add the preview label", "let someone test this PR", "publish a canary for this fix", or "how do I get a preview package for this PR". Specific to the withastro/astro monorepo and pkg.pr.new.

Analyze Astro CI test performance to find the slowest tests and produce a report with per-suite tables, platform breakdowns, and actionable recommendations. Use this skill whenever the user asks about CI test performance, slow tests, test timing, test duration, test speed, making tests faster, CI optimization, or anything related to profiling or benchmarking the Astro test suite. Also trigger when the user mentions "test perf", "slow CI", "CI takes too long", or "which tests are slowest".

Triage a bug report against the triagebot-action codebase. Reproduces the bug, diagnoses the root cause, verifies whether the behavior is intentional, and attempts a fix.

Triage a bug report. Reproduces the bug, diagnoses the root cause, verifies whether the behavior is intentional, and attempts a fix.

Use this skill whenever you are doing non-trivial engineering work in an existing git repository: fixing bugs, chasing regressions, extending or refactoring existing code, investigating why something is structured the way it is, or preparing a meaningful commit after real repo work. This skill is a working discipline for recovering prior context from git and writing new context back into history, so future agents can reconstruct not just what changed but why. Trigger even if the user never mentions git, history, or commit messages explicitly whenever they ask you to change code that already exists, mention an issue number, bug report, regression, earlier PR or commit, ask "why is this like this?", or need a fix in a repo with meaningful history. Prefer this skill for tasks where previous decisions, failed attempts, or linked commits are likely to matter. Do not trigger for one-off shell commands, throwaway snippets, pure read-only Q&A, or work outside a git repository.