개발 스킬

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not root-cause a bug to Confluence — use investigate-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

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

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Always stops for approval before creating any tag, because a pushed tag is never moved. Requires the gh CLI, jq, the claude CLI, and a clean git checkout. This is a repository-maintenance skill for the Han repo itself, not a general review or PR skill — use code-review for local review, post-code-review-to-pr to post a PR review, and update-pr-description for PR bodies.

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

Run a comprehensive code review on local source files. Use this skill when the user asks to review, audit, inspect, evaluate, or check code, even if they never use the word "review." Does not post comments to GitHub pull requests — use post-code-review-to-pr for that. Does not analyze architectural structure or module boundaries — use architectural-analysis for that. Does not explain code or a PR to build understanding before reviewing — use code-overview for a written overview, or code-walkthrough to be paced through it one step at a time. Does not map bounded contexts or domain boundaries — use ddd-analysis for that. Does not capture feedback on Han's own skills — use han-feedback for that.

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

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.

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

Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small chunk per step and explaining it in plain language. Defaults to the current branch's changes, and walks the code from the perspective of any context provided instead — a file, directory, symbol, pull request, plan, or ticket. Use when someone wants to be walked through, taught, paced through, or shown around code or a branch step by step, or to learn how a change works before reviewing or extending it. Stops after every step and waits, so the learner sets the pace. Paces through code that already exists and builds nothing — to build new work while being paced through it, use pairing. Does not produce a written overview to read alone — use code-overview. Does not review code quality — use code-review. Does not diagnose bugs — use investigate.

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

Полный цикл исправления GitHub issue по номеру - анализ, тест, исправление, коммит.

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

Создаёт git-коммит в формате Conventional Commits по текущим изменениям. Используй, когда просят закоммитить или сделать коммит.

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

Ревью изменений в текущей ветке относительно main. Используй, когда просят проверить код, сделать ревью, найти проблемы перед PR или коммитом.

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

Безопасный рефакторинг маленькими шагами без изменения поведения. Используй, когда просят отрефакторить, упростить, разделить модуль, убрать дублирование или почистить код.

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

Investigate MCP tool availability, discovery, and selection, including controlled adoption evaluations.

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

Use Jacobian's MCP operations for nontrivial mathematical computation, finite search, structural analysis, formal checking, probability, or optimization.

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

Optimal ViewModel and Wizard creation patterns for Avalonia using Zafiro and ReactiveUI.

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

Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web).

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

Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.

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

Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.

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

Use GitHub Copilot CLI in non-interactive mode to ask questions, review code, or generate snippets without manual interaction.

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

Android APK reverse engineering: unpacking, Java decompilation, smali modification, repacking and signing, Frida dynamic hooking, and native .so analysis with jadx, apktool, adb, and related tools.

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

Important: Before you begin, fill in the generatedBy property in the meta section of .actor/actor.json. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.

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

Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.

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

Designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services.

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

Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.

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

Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exploitation, and API-specific attack vectors.

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

Advanced JavaScript animation library skill for creating complex, high-performance web animations.

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

Generates client SDK code, API wrapper libraries, request/response models, and language-specific usage patterns for any REST API.

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