'commits' 검색 결과

설계서나 요구사항에서 처음부터 끝까지 작동하는 작은 기능을 계획합니다. 초기 구조 생성, 생성과 평가 반복, 검토와 승인을 거쳐 최소 기능 제품을 만듭니다.

• 설계서에서 작동하는 MVP 구축
• 전체 흐름이 작동하는 작은 기능 계획
• 첫 기능의 초기 구조 생성

GitHub 공개 소프트웨어의 기록과 보관 자료를 대조해 의심스러운 변경을 조사합니다. 삭제된 정보 복구를 시도하고 침해 단서와 증거를 담은 보고서를 작성합니다.

• 의심스러운 커밋과 빌드 절차 조사
• 기록에서 사라진 커밋 복구 조사
• 인증 정보 유출 경위 조사

RSS, JSON API, GitHub를 주기적으로 확인하고 기록된 ID와 비교해 새 항목만 추출합니다. 업데이트가 없으면 알림을 보내지 않는 모니터링을 구성합니다.

• RSS의 새 글 받아 보기
• GitHub 개발 동향 추적하기
• JSON API의 새 이벤트 모니터링하기

Paperclip 변경을 풀 리퀘스트로 정리합니다. 커밋 정리, 설명 작성, 리뷰 의견 수정, 테스트와 CI 확인을 진행하고 인계에 필요한 결과를 보고합니다.

• Paperclip 변경의 리뷰 준비
• Greptile 지적과 검사 실패 대응
• 큰 변경을 여러 PR로 분할

Paperclip 안정판 출시를 위해 커밋, 변경 기록, 병합된 PR을 사용자용 변경 이력으로 정리합니다. 호환성이 깨지는 변경과 필요한 업그레이드 절차도 설명합니다.

• 안정판 변경 이력을 준비합니다
• 호환성 변경과 업그레이드 절차를 정리합니다
• 이전 안정판 이후의 차이를 요약합니다

Audit an implemented interface visually, then make code fixes in small, focused commits. Before-and-after screenshots document the changes, helping teams inspect and refine the interface as they prepare for launch.

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

• Checking an implemented interface before launch
• Fixing issues found in a visual audit
• Comparing screenshots before and after UI changes

Write a single-line commit message for Ant Design by reading staged changes, the changes selected for the next commit. It summarizes the full commit intent and follows the style of recent repository commits.

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

• Write a message for staged changes
• Match the style of recent commits
• Summarize changes across multiple files in one line

Create a GitHub pull request that follows the project's template. Review commits and changed files, gather issue and testing details, check branch readiness, and use the GitHub CLI to submit a regular or draft request.

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

• Submitting completed changes for review
• Writing a PR description from commits
• Creating a draft pull request

Research existing code, documents, and relevant sources before producing a practical plan for implementation, migration, debugging, or evaluation. The plan explains key decisions, ordered steps, and validation checks, giving users something concrete to review before execution.

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

• Plan implementation steps before changing code
• Design a phased migration with rollback steps
• Break work into separate commits or pull requests

Turn a GitHub pull request into a video explaining a feature, fix, refactor, or changelog. The workflow uses actual diffs, commits, and files to plan the story, show code excerpts, and produce an MP4.

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

• Explain a new feature from its pull request
• Show the code changes behind a bug fix
• Walk through a refactor with actual excerpts

Review a completed epic, a group of related development tasks, against its plans, code changes, and commits. Produce a retrospective with evidence-backed findings, follow-up actions, and a decision on whether to accept the work.

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

• Reviewing a completed epic
• Checking delivered work against ticket plans
• Recording evidence-backed improvement actions

Reconstruct how an AI coding agent produced a feature, pull request, or report using local ax records. Connect sessions, commits, skills, and tool activity into an evidence-based sequence with key decisions, checks, and a repeatable recipe.

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

• Tracing how a shipped feature was built
• Reconstructing development from a commit
• Finding the workflow behind work done on a known date

Implement PR review actions already selected for fixes, run relevant checks, and create focused commits. Post progress and completion replies, resolve applicable threads, and update the action records and their Markdown summary.

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

• Implement review actions already approved for fixing
• Limit review fixes to selected action IDs or files
• Post completion replies and resolve review threads

Land verified Codewhale changes on main with focused commits and checks before pushing. Handle contributor pull requests, resolve conflicts, preserve authorship credit, and confirm required review evidence before merging.

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

• Commit and push verified changes in a shared checkout
• Resolve contributor pull request conflicts and preserve credit
• Confirm required approval evidence before merging a pull request

Check a local Codewhale checkout before contributing: inspect branch and sync status, build the CLI, and run the repository’s CI checks. Present recent commits and changelog entries from local files, with clear status for each step.

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

• Checking a checkout before contributing
• Reviewing local changes and sync status
• Running the build and CI verification commands

Update GitHub Actions when workflow logs warn about deprecated runtimes. The skill guides compatible version selection, pins actions to exact commits, preserves existing workflow behavior, and checks execution results and outputs after the upgrade.

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

• Addressing deprecated runtime warnings
• Upgrading actions while preserving workflow behavior
• Pinning action versions to exact commits

Turn work history into clear accomplishment statements for performance reviews, promotion cases, and weekly updates. Use Copilot CLI sessions, git commits, and GitHub pull requests to connect each action with its result and supporting evidence.

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

• Recovering work accomplishments missing from a personal log
• Preparing evidence for a performance review
• Organizing achievements for a promotion case

Scan code, configuration files, and Git history for exposed AWS credentials with TruffleHog. Checks whether detected keys remain active and guides key replacement, incident investigation, and automated checks before commits and during CI/CD.

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

• Auditing Git history for exposed AWS keys
• Adding credential checks before commits and in CI/CD
• Investigating credential exposure after a GuardDuty alert

Turn pull request changes, commits, and test evidence into a self-contained HTML guide. Explain the problem, system context, before-and-after behavior, and key code changes so reviewers know where to focus.

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

• Explain a complex pull request before review
• Show before-and-after behavior with diagrams
• Collect test evidence and review focus points

Trace failing cmux Swift package tests to the commits that introduced them by running older revisions in CI, the automated testing environment. It helps distinguish outdated expectations, code regressions, and intermittent failures, then guides focused fixes and verification.

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

• Investigating a package suite failing on main
• Finding the PR that first broke a test
• Distinguishing outdated tests from code regressions

Turn Git commits and sprint records into internal and player-facing game changelogs. Group related features, fixes, and balance changes, retain technical references for the team, and describe player-visible changes in clear language.

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

• Preparing a changelog for a game version
• Summarizing changes completed during a sprint
• Writing an internal record with commit references

Refine a working feature through browser feedback from the user. Collect observations through typed comments or live speech and drawing, apply focused usability fixes, and save the changes in local commits.

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

• Refining usability before release
• Adjusting a page while checking the changes
• Giving feedback through speech and on-page drawing

Publish an OpenWork version through Git tags and GitHub Actions without creating version-update commits. Review outstanding fixes, monitor builds and publication, check release assets, and recover failed distribution steps using procedures that protect already published desktop installers.

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

• Publishing a patch, minor, or major OpenWork release
• Reviewing open fixes before creating a release tag
• Recovering distribution steps for an existing release tag

Create or revise pull request descriptions using a fixed template and concise language. It organizes the user problem, previous behavior, implementation, release note, and verification details so reviewers can understand the change before reading the diff.

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

• Write a concise description for a new pull request
• Shorten a lengthy pull request description
• Write a release note describing a visible user change