스킬 찾기

Set up Loop Engineering through a single command-line tool, choosing a workflow pattern and agent tool. Start in report-only mode, check setup health and readiness, and provide next actions and first-run instructions.

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

• Introducing a daily issue and priority review workflow
• Setting up workflows for stalled pull requests or failing CI
• Checking the health of an existing Loop Engineering setup

Scans merged pull requests and commits since a chosen reference, using titles, labels, milestones, and messages to categorize changes. Produces a release notes draft, highlights breaking changes and security items, and records the scan window.

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

• Collecting changes since the previous release tag
• Sorting updates into features, fixes, and other categories
• Identifying breaking changes and security items

Track open pull requests, proposed code changes awaiting integration, and identify blockers in automated checks, reviews, conflicts, and unanswered comments. Receive a prioritized watchlist and the top three actions for a human to take.

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

• Monitor the status of open pull requests
• Find failing checks, conflicts, and unanswered review comments
• Assess merge readiness against project requirements

Turn scan data into a categorized release notes draft covering features, fixes, breaking changes, and security. Get clean Markdown suitable for a CHANGELOG or GitHub release, with a review disclaimer and human approval required before publication.

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

• Draft release notes from scan results
• Organize features, fixes, breaking changes, and security updates
• Prepare Markdown for a CHANGELOG or GitHub release

Review merged pull requests and significant commits within a release window, then organize features, fixes, breaking changes, and security signals into structured source material for drafting release notes.

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

• Collecting changes since the last release
• Checking breaking changes and security signals
• Preparing source material for release notes

Turn a structured change list into a categorized release notes draft for users. Follow the project's writing style, highlight breaking changes and security items, and include upgrade guidance where evident, leaving publication to human review.

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

• Drafting release notes from a structured change list
• Organizing features and bug fixes for users
• Highlighting breaking changes and security updates

Review dependency manifests and lockfiles to find outdated packages and known security vulnerabilities. Group proposed updates by version change, report current and suggested versions, and identify updates that need human review.

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

• Reviewing outdated dependencies
• Checking known vulnerabilities and update options
• Separating patch, minor, and major updates

Analyze failures in CI, the automated checks run during development. Identify the failing job and step, classify the likely cause, and suggest a small fix, continued monitoring, or human review.

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

• Identifying failed jobs and steps in CI
• Distinguishing intermittent failures from code regressions
• Routing environment failures to a human

Scan merges and commits since the previous release to collect user-facing changes for a changelog. Produce structured entries and a summary, with explicit lists of breaking changes and security signals.

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

• Collecting changes since the previous release
• Organizing user-facing updates
• Listing breaking changes and security signals

Review open issues and discussions to create a clear work queue. Record the five highest-priority items, suggested labels, possible duplicates, and cases needing human judgment in a state file for future reviews.

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

• Prioritizing a backlog of open issues
• Finding possible duplicate reports
• Preparing label suggestions

Fix one clearly defined code issue, such as a failed automated check, review comment, or typo, with the smallest necessary change. Run relevant tests and summarize the changes, verification results, and any need for human review.

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

• Fixing a specific automated check failure
• Addressing one actionable review comment
• Correcting a typo in code

Inspect recent merges for leftover debug code, TODO comments, lint warnings, and technical debt, meaning deferred maintenance work. Create a prioritized cleanup list that separates small fix candidates from issues requiring human judgment.

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

• Finding debug code left after merging
• Organizing TODO and FIXME follow-up work
• Prioritizing newly introduced lint warnings

Review dependency files to find outdated packages and security vulnerabilities. Sort updates by severity and version change, identify cases needing human review, and record a prioritized update list with testing requirements.

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

• Prioritizing outdated dependencies
• Separating security fixes by severity
• Identifying major updates needing human review

Drafts a token budget extension request when an autonomous loop approaches its daily limit and high priority work remains. Uses logged results and remaining issues to justify the request, then pauses until a human increases the budget.

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

• Requesting extra budget for remaining critical work
• Summarizing daily token spending and successful actions
• Preparing a budget request for a human maintainer

Independently checks code changes against the original issue, runs tests, and verifies that edits stay within scope. Produces an approval, rejection, or request for human judgment, supported by test results and specific findings.

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

• Independently reviewing another agent's implementation
• Checking that a CI failure was actually fixed
• Finding unrelated edits or disabled tests

Independently review release note drafts against scanned change data. Check factual accuracy, missing items, tone, links, and clear coverage of breaking changes and security updates, then return a verdict with recommended revisions.

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

• Checking release notes against scanned changes
• Reviewing breaking change and security notices
• Finding missing links and acknowledgments

Scan recent merges to main for unfinished tasks, deprecated APIs, broken documentation links, and obsolete feature flags. Get a concise report with file locations, risk, effort, and suggested follow-up actions for each merge.

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

• Find cleanup tasks after merging changes
• Check for deprecated APIs and broken documentation links
• Identify feature flags scheduled for removal

Load project rules before an agent starts work, then apply restrictions to file edits, tests, pushes, and merges. Check pause settings and identify actions that require human approval.

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

• Applying project rules before automated work
• Checking protected paths before editing
• Reviewing push and merge conditions

Review open pull requests, or proposed code changes, for automated checks, approvals, blocking comments, and conflicts. Assess whether project requirements allow merging, and suggest a next step such as a small fix, rebase, or human review.

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

• Reviewing the status of open pull requests
• Identifying blockers before merging
• Choosing the next action after a failed check

Check estimated token usage against daily limits before and after each automated loop run. Switch to reporting only, exit early when required, and record run outcomes so repeated agent work stays within configured limits.

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

• Checking daily token usage before a run
• Switching to reporting only near budget limits
• Exiting early when there is no actionable work

Turns changelog-scan results into a readable, categorized release notes draft. Places breaking changes and security items at the top and ends with a human review note, providing a proposal for review.

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

• Turning scan results into a release notes draft
• Organizing release updates by category
• Highlighting breaking changes and security items

Review recent changes, automated test failures, issues, and conversations to prioritize engineering work. Produce a concise report separating urgent actions, watch items, noise, and state updates, with suggested next steps and rough effort estimates.

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

• Prioritizing recent CI and test failures
• Sorting team issues and conversation findings
• Separating urgent work from items to monitor

Classify failures in CI, automated checks run during development, to distinguish code regressions, temporary infrastructure problems, security test failures, and inconsistent results. Record each failure's category, suggested next action, and attempt count in a structured report.

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

• Sort failed CI checks by likely cause
• Identify small regressions that may qualify for automatic fixes
• Refer infrastructure and security failures to a human

Scan recent merges, pull requests, and commits for release note material. Produce structured entries and a summary with PR references, highlighting breaking changes and security items while filtering routine dependency and bot noise.

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

• Gathering release note material from recent changes
• Identifying breaking changes and security items
• Organizing changes with PR references