병합
main-to-next 병합 과정을 처리합니다. 이 스킬은 각 단계별 서브 스킬을 포함합니다:
- resolve-conflicts.md — Git 병합 충돌 해결
- fix-ci.md — 빌드 오류, 타입 오류, 테스트 실패 수정
- clean-changesets.md — 오래된 changeset 파일 정리
호출되면 step 인자를 확인하여 실행할 서브 스킬을 결정한 후, 해당 파일의 지침을 읽고 따릅니다.
main-to-next 병합 작업(충돌 해결, 변경셋 정리, CI 수정)을 처리합니다. main을 next로 병합할 때 사용하세요.
이 스킬은 Astro 프로젝트에서 `main` 브랜치를 `next` 브랜치로 병합하는 과정을 자동화합니다. 병합 과정은 여러 단계로 나뉘어 있으며, 각 단계는 별도의 서브 스킬로 구현됩니다. `resolve-conflicts` 서브 스킬은 git 병합 충돌을 해결하고, `fix-ci` 서브 스킬은 빌드 오류, 타입 오류, 테스트 실패를 수정하며, `clean-changesets` 서브 스킬은 오래된 changeset 파일을 정리합니다. 사용자는 `step` 인자를 통해 특정 단계를 실행할 수 있으며, 각 단계의 지침은 해당 마크다운 파일에 상세히 기술되어 있습니다. 개발자 워크플로우에서 반복적이고 오류가 발생하기 쉬운 병합 작업을 안정적으로 처리하여 생산성을 높입니다. Claude Code, Cursor 등 AI 에이전트와 함께 사용하도록 설계되었습니다.
npx skills add https://github.com/reyalka/astro/tree/HEAD/.agents/skills/mergemain-to-next 병합 과정을 처리합니다. 이 스킬은 각 단계별 서브 스킬을 포함합니다:
호출되면 step 인자를 확인하여 실행할 서브 스킬을 결정한 후, 해당 파일의 지침을 읽고 따릅니다.
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".