개발 스킬

Submit a new Wall of Apps entry or update an existing one using the `asc apps wall submit` CLI flow. Preview the proposed change first, then review the pull request plan and the resulting entry update.

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

• Adding an App Store app to Wall of Apps
• Updating an existing Wall of Apps entry
• Submitting a TestFlight or pre-release app

Bulk-create or update localized display names for subscriptions, subscription groups, and in-app purchases across App Store locales. It can also handle descriptions where supported, using version-scoped asc commands and checking existing entries before writing changes.

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

• Localizing subscription names across App Store locales
• Updating display names for in-app purchases
• Filling missing subscription group names in several languages

Automate iOS simulator screenshot workflows: build and launch an app, capture screens through AXe, add device frames, review the resulting images, and upload them with asc. Useful for preparing localized screenshot sets as well as single captures.

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

• Capture app screens from an iOS simulator
• Frame screenshots for App Store listings
• Prepare and upload localized screenshot sets

Turn a codebase into Mermaid diagrams such as architecture, ER, sequence, class, and flow diagrams. It analyzes relevant files, writes diagram source, renders SVG and PNG images, and checks the rendered result for readability and correctness.

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

• Visualize a codebase architecture
• Create an ER diagram from database models
• Show an API flow as a sequence diagram

Plan and build MCP servers that let AI agents work with external APIs through tools. The guide covers research, implementation, testing, and registration, with patterns for Python FastMCP and the Node/TypeScript SDK, including schemas, pagination, authentication, and useful error messages.

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

• Build an MCP server for an external API
• Choose tools and schemas for an MCP integration
• Test and register a Python or TypeScript server

Revise an existing agent skill in response to feedback. The skill guides the agent to inspect the skill files, plan focused changes, update instructions or supporting scripts, and validate the result before packaging it.

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

• Fixing a skill after reporting a bug
• Improving unclear skill instructions
• Adding a requested capability to a skill

Review JSON execution traces and user feedback to find where a skill fails, takes too many steps, or uses too many tokens. Identify likely causes and apply focused improvements to the skill’s existing instructions or scripts.

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

• Find recurring failures in skill execution logs
• Improve a skill using real run history
• Apply feedback to an existing skill

Investigate an agent run by reviewing its execution trace, a record of steps and tool calls. Start with a run overview, then inspect relevant inputs, outputs, errors, and token use to explain what happened or diagnose a failure.

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

• Finding why an agent run failed
• Reviewing the steps and tools an agent used
• Checking token usage and efficiency

Build and launch an MVP, from product scope and landing page through implementation, payment integration, deployment, and quality checks. It also outlines post-launch monitoring, including checks for uptime, core flows, payments, errors, and performance.

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

• Turn a product idea into a scoped MVP
• Build a landing page and integrate payments
• Deploy an existing project and check core flows

Maintain documentation that AI agents can discover and read. This skill explains the requirements for `llms.txt` indexes, page Markdown, skill and MCP discovery endpoints, and HTML-to-Markdown parity, with guidance for keeping these checks intact as docs change.

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

• Adding a new documentation section or product area
• Updating `llms.txt` indexes or Markdown page routes
• Changing skill or MCP discovery endpoints

Capture before-and-after screenshots of changed Sentry UI in the real app, organize them by page and state, and attach them to a pull request description. The skill also checks image differences and removes sensitive values before upload.

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

• Showing reviewers a frontend change in context
• Comparing UI before and after a change
• Documenting changed and unchanged screens across states

Work through a pull request’s actionable CI failures and high or medium priority review feedback. Diagnose root causes, make and verify fixes, then monitor checks and new feedback in a loop, stopping when only human approval or merge gates remain.

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

• Fix failing CI checks on an open pull request
• Address high or medium priority review feedback
• Repeat check and feedback cycles after pushing fixes

Create or update concise AGENTS.md and CLAUDE.md files that give coding agents actionable project guidance. Inspect existing commands, conventions, and documentation, then point to authoritative references instead of duplicating them.

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

• Setting up agent instructions for a repository
• Updating outdated AGENTS.md guidance
• Keeping project rules concise and reference-backed

Create a Git branch using Sentry naming conventions. Determine the work type and a short ASCII, kebab-case description from the provided request or local changes, choose a base branch using repository information, avoid name collisions, and report the branch created.

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

• Starting a new feature or fix on a branch
• Creating a branch based on current local changes
• Naming a branch according to Sentry conventions

Document Sentry API endpoints with OpenAPI schemas, typed responses, and request parameters. Compare declared types with runtime responses, reuse canonical response types, migrate legacy path docs, and validate the generated specification.

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

• Adding OpenAPI documentation to an endpoint
• Correcting response or parameter types
• Checking declared schemas against runtime responses

Refine recently changed code to make it clearer and easier to maintain while preserving its behavior. The skill follows project-specific conventions, removes unnecessary complexity, and favors readable, explicit code over compact tricks.

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

• Cleaning up recently changed code
• Reducing nesting and redundant abstractions
• Improving readability while preserving behavior

Remove assigned Python modules from mypy exclusion settings in pyproject.toml, fix typing issues within the agreed scope, and run the requested checks. Return a structured batch summary covering changed modules, fixes, validation, and remaining blockers.

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

• Work through a scoped batch of Python typing debt
• Remove assigned modules from mypy exclusions
• Summarize typing fixes and validation for an orchestrator

Add a GitHub issue reference and, when available, its linked Linear ticket to the current pull request description. The skill checks the issue’s linkback comment, preserves the existing description, and replaces an existing Issues section instead of duplicating it.

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

• Adding an issue reference to the current pull request
• Including the Linear ticket linked from a GitHub issue
• Updating an existing Issues section in a PR description

Review pull requests and code changes using Sentry engineering practices. Check for runtime errors, performance problems, security risks, design mismatches, and test gaps, then give polite, actionable feedback focused on reducing risk rather than enforcing personal style preferences.

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

• Reviewing a pull request for correctness and risk
• Checking changed code for security or performance issues
• Assessing design choices and test coverage

Inspect a repository’s languages, frameworks, build tools, services, and existing Claude Code settings. Generate a project-specific `settings.json` permissions allowlist containing read-only commands, with MCP suggestions when relevant.

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

• Setting up Claude Code permissions for a project
• Reviewing an existing settings.json
• Choosing safe read-only shell commands

Create or improve agent skills by gathering and synthesizing source material, writing skill files, refining their descriptions, and handling registration and validation. The workflow also supports updates based on positive or negative examples and maintenance of skill documentation.

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

• Creating a new agent skill from source material
• Updating a skill after positive or negative examples
• Maintaining skill documentation and registration

Draft commit messages or guide commits using Sentry-style Conventional Commits. Choose an allowed change type, write a concise subject and useful body, and add issue references or breaking-change notes while avoiding personal or sensitive information.

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

• Drafting a commit message for a code change
• Formatting a commit with an issue reference
• Writing a breaking-change footer

Prepare or refresh a pull request title and reviewer-facing description based on the full branch diff. Explain the change and its effects in a concise form, adding migration, compatibility, risk, or review guidance when it helps reviewers assess the work.

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

• Draft a title and description for a new pull request
• Refresh PR text after the branch scope changes
• Explain a breaking API or configuration change to reviewers

Review Django code for verified performance problems such as repeated database queries, unbounded querysets, missing indexes, and write loops. Trace how data is used and confirm scale and impact before reporting findings with evidence and suggested fixes.

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

• Find confirmed N+1 queries in a Django view or serializer
• Review queryset behavior on a high traffic endpoint
• Check for unbounded querysets that may exhaust memory