스킬 찾기

Updates Claude Code CLI release tracking within the Claude Code Ultimate Guide, following its documented workflows. It can also handle an explicitly requested guide version bump and report changes, verification results, and unresolved checks.

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

• Updating Claude Code CLI release tracking in the guide
• Synchronizing the latest CLI version with the landing page
• Updating the guide version when explicitly requested

Audit French and English whitepapers and recap cards for outdated versions, missing language counterparts, and metadata problems. Receive document scores, an overall health report, and prioritized update suggestions, with optional proposed patches.

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

• Find whitepapers that lag behind the current guide
• Check French and English document pairs
• Identify missing or inconsistent metadata

Check Claude Code configuration against a supplied threat database. Review installed skills, MCP servers that connect external tools, hooks, permissions, and exposed credentials, then receive findings grouped by severity with prioritized actions.

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

• Review configuration after installing skills or MCP servers
• Find overly broad permissions and dangerous settings
• Check configuration files for exposed keys and tokens

Turn an agreed product direction into a technical specification before coding. Create architecture and flow diagrams, define failure handling and input validation, and map tests to the behavior engineers need to implement.

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

• Define architecture before implementing a complex feature
• Map background jobs and external API interactions
• Check failure recovery paths and test coverage

Check whether a guide and its landing site show matching versions, template counts, and quiz totals. Get a structured status report that identifies mismatches, points to affected files, and suggests specific corrections.

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

• Checking landing site figures after a guide update
• Finding mismatched template and quiz counts
• Identifying files that need synchronization fixes

Check a Proofpack release candidate before packaging by running tests, validating the candidate, and inspecting the package locally. Compare the source state and command results with the evidence log, then report passed, failed, or unknown checks.

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

• Checking a Proofpack candidate before packaging
• Comparing local verification with recorded evidence
• Finding unverified checks or uncovered changes

Turn Git commits and pull request details into release notes in three formats: a changelog section, a release PR description, and a user announcement. Group changes, explain user impact, and flag database migrations.

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

• Prepare a changelog for a release
• Draft a release pull request description
• Explain updates to users in plain language

Compare a saved baseline of Anthropic documentation with the current local snapshot, showing added, removed, and modified sections, line changes, and unchanged counts without making a network request.

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

• Reviewing changes between saved documentation snapshots
• Finding added or removed documentation sections
• Checking line changes and unchanged section counts

Review a pull request for code quality, correctness, security, tests, and documentation. Receive structured findings ranked by severity, with file references, approval status, positive highlights, and questions that need clarification.

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

• Reviewing a pull request before merging
• Checking changes against the original plan
• Auditing error handling and validation of AI output

Suggests running verbose shell commands through RTK, a tool that condenses command output, and executes them after confirmation. It helps reduce the text an AI agent processes when reviewing Git history, tests, builds, and files.

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

• Reducing output when reviewing Git history and diffs
• Condensing long test and build results
• Reading large files with less command output

Analyze SonarCloud findings for a pull request, a proposed code change. Group issues by severity, type, file, and rule, then produce a report highlighting frequent problems and recommended priorities without modifying code.

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

• Reviewing quality findings before merging a pull request
• Finding files and rules with the most issues
• Prioritizing bugs and security findings

Turn articles, transcripts, or notes into a structured talk summary. Identify whether the material centers on practical experience or ideas, then extract its narrative, themes, sourced metrics, and gaps to guide further preparation.

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

• Starting a talk from an article or notes
• Assessing source material before committing to a talk
• Organizing measurable results with their sources

Review a feature request before coding to clarify the user’s real goal and challenge assumptions. Choose whether to expand, hold, or reduce scope, then receive a recommendation to proceed, reframe the brief, or reject the direction.

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

• Clarify the purpose behind a feature request
• Explore a broader product direction
• Find gaps in a plan with fixed scope

Turn a feature request into an implementation plan before coding. Five planning phases cover requirements, interface design, technical choices, research, and metrics, producing ordered tasks, a test plan, and records explaining major decisions.

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

• Planning a feature that touches several files
• Resolving unclear requirements before implementation
• Recording architecture and interface decisions

Run a quick code security review for exposed credentials, injection risks, unsafe page content, vulnerable dependencies, and authentication issues. Receive findings grouped by severity, with file locations and suggested fixes to prioritize remediation.

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

• Reviewing sensitive code changes before merging
• Checking for exposed credentials
• Reviewing authentication and injection risks

Compare three or four ways to frame a talk, with strengths, weaknesses, and audience fit. Generate titles, conference proposal descriptions, and a peer feedback draft, then confirm the chosen direction before scripting.

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

• Compare possible angles for a talk
• Draft a conference proposal
• Choose a talk title

Check release readiness by reviewing tests, type checks, linting, builds, security findings, documentation, and environment settings. Get a report separating deployment blockers from warnings, plus action items and checks for post-deployment health and rollback preparation.

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

• Checking readiness before a production deployment
• Reviewing staging environment settings
• Adding release checks to CI/CD

Save an unfinished session as a timestamped Markdown handoff. Capture changed files, decisions and their reasons, current progress, blockers, and ordered next steps so work can resume later or continue in another Claude instance.

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

• Saving unfinished work before ending a session
• Preserving progress before switching tasks
• Recording decisions before context compaction

Develop a confirmed talk angle and title into a five-act script with speaker notes and timing. Receive a slide-by-slide specification and a completed prompt to paste into Kimi for presentation generation.

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

• Writing a full script after confirming the talk direction
• Planning speaking time and pauses
• Preparing slide specifications for a designer

Review an implementation plan before coding across architecture, code quality, tests, and performance. Compare concrete options for each issue, explain effort and risks, and choose a direction through an interactive review.

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

• Review a specification before implementation
• Check component boundaries and dependencies
• Find missing tests and failure scenarios

Turn a talk summary and optional timeline into a numbered, categorized catalogue of ideas. Rate each idea's presentation potential and receive suggestions for grouping strong concepts into a talk structure before choosing an angle.

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

• Listing ideas before choosing a talk angle
• Comparing concepts for demonstrations and concrete evidence
• Grouping related ideas into a talk structure

Answer a short series of questions about your workflow to choose a Claude Code agent, command, skill, hook, or rule, then generate a template with the structure and file location for that component.

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

• Choosing how to implement a Claude Code workflow
• Creating a template for a reusable team procedure
• Planning automatic checks or persistent behavior rules

Turns Git commits and pull request details into release notes for CHANGELOG.md, a release pull request, and Slack. It categorizes changes, explains user impact in plain language, and flags database migrations that need attention.

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

• Preparing release notes since the last release
• Summarizing changes across a specified version range
• Drafting a release pull request body

Review code changes for concrete defects. Use it to examine modified code when you want to check whether a change contains a bug, with the review focused on specific problems in the changes.

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

• Reviewing changes after editing code
• Checking a bug fix for further defects
• Reviewing code changes that add a feature