스킬 찾기

개발 스킬의 첫 사용에 앞서 작업 관리 위치, 분류 라벨, 용어집과 설계 결정 기록의 위치를 확인합니다. 사용자 검토를 거쳐 저장소 공통 설정 문서를 정리합니다.

• 개발 스킬의 초기 설정
• 작업 관리 위치와 분류 라벨 정리
• 용어집과 설계 결정 기록의 위치 결정

Prepare code changes for sharing by merging the base branch, running tests, and reviewing the diff. Update VERSION and CHANGELOG, then commit, push, and create a pull request, a proposal to merge the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a pull request for completed work
• Test and review changes before pushing
• Merge the base branch before sharing changes

Review proposed code changes before merging them. Compare changes with the base branch to find structural issues, including unsafe SQL, misplaced trust in large language model inputs, and unintended effects within conditional code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request before merging
• Checking SQL changes for safety
• Checking which AI inputs the code trusts

Monitor a live app after deployment for console errors, slower performance, and page failures. Periodic screenshots and comparisons with pre-deployment baselines help identify anomalies and check whether the release is behaving as expected.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitoring a live app after deployment
• Checking for performance regressions after a release
• Comparing screenshots before and after deployment

Run sequential reviews of a plan from business, design, engineering, and developer experience perspectives. Apply six principles to intermediate decisions, then bring close choices, scope questions, and reviewer disagreements to a final approval step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a plan from several perspectives
• Running reviews without answering every intermediate question
• Considering close choices and disagreements at final approval

Merge an existing pull request, wait for automated checks and deployment, then verify production health with canary checks, targeted checks for problems. Continue the release workflow after /ship has created the pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Merging an existing pull request
• Waiting for CI and deployment to finish
• Checking production health after a release

Review a product or business plan from a founder’s perspective. Challenge assumptions and reconsider the problem, then explore whether to expand the scope, add selected ideas, keep it fixed, or reduce it to essentials.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reconsidering a product plan’s assumptions
• Exploring a more ambitious product direction
• Choosing which scope expansions to include

Find and fix bugs in websites, APIs, command-line tools, and background processes. Choose from three testing depths, verify fixes, and receive evidence of the changes plus a summary of readiness for release.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test a website and fix bugs
• Check API or command-line behavior
• Verify background jobs and webhook processing

Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating project documentation after a release
• Checking architecture diagrams against shipped changes
• Polishing changelog entries and organizing TODOs

Review a UI/UX plan before implementation, score its design dimensions, and identify missing decisions. Through discussion, the skill adds concrete improvements directly to the plan so the review produces an updated plan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a UI/UX plan before implementation
• Finding missing design decisions
• Adding design critique directly to a plan

Use OpenAI Codex CLI to review code changes, challenge an implementation by looking for ways it could fail, or discuss technical questions. Three modes provide an independent opinion, with follow-up questions supported in ongoing consultations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Get an independent review of code changes
• Challenge code to uncover possible failures
• Continue a technical consultation with follow-up questions

Review plans for APIs and developer tools through the eyes of their users. Explore developer needs, compare competitors, and identify onboarding friction, with modes for competitive differentiation, detailed refinement, or critical gaps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing an API or SDK plan
• Finding friction in developer onboarding
• Comparing developer experience with competitors

Create missing documentation for a feature, module, or whole project. Use Diataxis, a framework that separates tutorials, practical guides, reference information, and explanations, to organize documents around what readers need to learn or accomplish.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing documentation for an undocumented feature
• Creating tutorials and practical guides
• Preparing module references and explanations

Audit a developer product by trying its documentation and setup flow, measuring onboarding time, capturing errors, and reviewing command-line help. Produce an evidence-backed scorecard and compare results with earlier planning scores when available.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Try a developer product's documentation and setup flow
• Measure onboarding time
• Review error messages and command-line help

View release versions claimed by open pull requests, proposed code changes, alongside work in related Conductor workspaces. Get a read-only snapshot showing queued work and the version slot that /ship would choose next.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking versions claimed by open pull requests
• Reviewing upcoming work across related workspaces
• Finding the version slot /ship would choose next

Review a week of engineering work using commit history, work patterns, and code quality measures. It tracks trends across retrospectives and breaks down each team member’s contributions, highlighting strengths and areas for growth.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review the week’s engineering work
• Summarize work completed during a sprint
• Reflect on each team member’s contributions

Inspect proposed changes in GitHub, GitLab, or Perforce for review feedback, failed automated checks, and incomplete descriptions. It separates actionable findings from informational or resolved comments, then helps fix issues and close addressed review threads when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspect a change before submission
• Identify failed checks and required fixes
• Organize human and bot review feedback

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check pull request changes for vulnerabilities before merging
• Add Strix scans to GitHub Actions or GitLab CI
• Choose between managed reviews and scans on your own runners

Build GitLab workflows that automate building, testing, and deployment. The skill covers pipeline stages, dependency caching, runners that execute jobs, and manual approval before production deployment, with examples for Docker, Kubernetes, and Terraform.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating builds and tests in GitLab
• Reviewing caches to improve pipeline performance
• Separating staging and production deployments

Design CI/CD pipelines that move applications through development, staging, and production. Define approval and security checks, gradual release strategies, health checks, and rollback procedures, and investigate gates or deployments that fail to progress.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing CI/CD pipelines across multiple environments
• Introducing canary or blue-green releases
• Investigating stalled approvals and release gates

Manage API keys, passwords, and certificates used in CI/CD, the automated process for testing and deploying software. Connect secret stores, plan credential rotation, restrict access, and prevent sensitive values from appearing in logs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Moving API keys and passwords out of source code
• Connecting CI/CD pipelines to secret stores
• Planning automated or manual credential rotation

Create GitHub Actions workflows to automate testing, builds, and deployments. Includes patterns for Docker image publishing, Kubernetes deployment, security scans, and testing across multiple environments, plus reusable workflows and approval steps for production releases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating tests for pushes and pull requests
• Building and publishing Docker images
• Deploying to Kubernetes with production approvals

Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an onboarding guide for a codebase
• Mapping system architecture and dependencies
• Planning a legacy system migration or rewrite

Convert plain text documents into Markdown while preserving their content. Follow supplied formatting rules or a reference file, organize headings, lists, and code blocks, and clean up spacing for the chosen publishing platform.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Converting text manuals into Markdown
• Matching formatting across related documents
• Cleaning up spacing in converted Markdown