Manejar tareas de fusión de main a next, incluyendo resolución de conflictos, limpieza de changesets y correcciones de CI. Útil al fusionar main en next.
Este skill automatiza el proceso de fusión de la rama `main` a `next` en un repositorio de Astro. Está diseñado para desarrolladores que necesitan realizar fusiones regulares y garantizar que la rama `next` se mantenga estable y actualizada. El skill se compone de tres sub-skills: `resolve-conflicts.md` para resolver conflictos de fusión de Git, `fix-ci.md` para corregir errores de compilación, tipo y fallos en pruebas, y `clean-changesets.md` para eliminar archivos changeset obsoletos que ya no son relevantes. Cuando se invoca, revisa el argumento `step` para determinar cuál sub-skill ejecutar, luego lee y sigue las instrucciones de ese archivo. Es útil en entornos donde se utiliza Git y sistemas de CI como GitHub Actions, facilitando la automatización de tareas repetitivas y propensas a errores.
npx skills add https://github.com/reyalka/astro/tree/HEAD/.agents/skills/mergeManejar el proceso de fusión de main a next. Este skill tiene sub-skills para cada etapa:
Cuando se invoque, revisar el argumento step para determinar cuál sub-skill ejecutar, luego leer y seguir las instrucciones de ese archivo.
This repo contains 7 individual skills — each has its own dedicated page.
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".
Independently implement and validate an alternative solution for an Astro pull request. Use only for Factory's adversary blue team.
Qualify and compare red and blue solutions for an Astro pull request using Astro-specific merge and tie-break criteria. Use only for Factory's adversary purple team.
Perform a static, read-only code review of an Astro pull request or of a local branch, commit range, diff, patch, or working tree being prepared as a pull request. Determine whether the change satisfies its stated business requirements and is good enough to merge, using the PR description, linked requirement issues and roadmap items, and PR or issue discussions when available. Use this skill only for PR review or self-review, not issue triage or bug investigation. It reports only merge-relevant findings and never edits code or runs project code, tests, builds, checks, or scripts.
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.
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.
How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".