'commits' 검색 결과

Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.

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

• Implementing tasks from plan.md
• Following the test-driven development cycle
• Verifying completion at phase checkpoints

Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.

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

• Preparing issues using repository templates
• Creating branches with the required naming format
• Grouping changes into clear commits

Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.

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

• Preparing a concise daily standup update
• Turning rough work notes into a shareable report
• Summarizing commits, pull requests, and ticket changes

Re-review a GitLab merge request after new commits, track the outcome of every previous finding, and inspect both new changes and the full proposal. Verify the current code, then publish a test report and review verdict.

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

• Re-reviewing a merge request after fixes
• Tracking the resolution of earlier review findings
• Checking new commits for regressions and incomplete fixes

Re-review a pull request after new commits arrive. Check every previous finding, inspect the new changes for regressions, and review the full current change. Run relevant verification and publish a test report and review verdict within Factory.

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

• Checking whether previous review findings were addressed
• Finding regressions introduced by follow-up commits
• Re-running tests against the current PR head

Prepare an OpenSEO release by updating the version, selecting user-visible changes from commits, and writing concise release notes. Review agents check the draft against the code before a pull request is opened for the release.

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

• Prepare an OpenSEO release pull request
• Summarize changes since the previous release
• Update the version and release notes together

Turn Git commits, records of code changes, into clear release notes for users. The skill groups updates by type, rewrites technical descriptions in plain language, and filters out internal work such as refactoring and tests.

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

• Preparing release notes for a new version
• Summarizing weekly or monthly product updates
• Writing app store update descriptions

Investigate Sentry errors by fetching event details and the actions leading up to failures through Composio CLI. Connect error locations to local code, inspect suspect commits, propose patches, run tests, and rank unresolved issues.

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

• Investigate a new Sentry alert
• Trace a regression to suspect commits
• Rank unresolved errors by frequency

Complete small development tasks with a plan, focused commits, and recorded progress. Add discussion, research, or verification when needed, and use task listings and status checks to find and resume unfinished work.

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

• Completing a small fix with a recorded plan and commits
• Checking progress across accumulated quick tasks
• Resuming an unfinished task

Create a pull request branch from the current branch while excluding .planning/ commits. This keeps planning documents out of the review so reviewers can focus on the code changes.

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

• Prepare a PR branch focused on code changes
• Exclude planning document commits from review
• Create a review branch for a chosen target branch

Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.

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

• Preparing a concise daily standup update
• Turning rough work notes into a shareable report
• Summarizing commits, pull requests, and ticket changes

Compare code structure across two commits, tags, or directories to identify security-relevant changes. Produces a report on new attack paths, privilege boundaries, complexity, and how widely a change could affect other functions.

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

• Compare code structure before a release
• Investigate new attack paths after code changes
• Track untrusted data flows across a refactor

Read staged Git changes and suggest a message in Conventional Commits format, a structured way to describe changes. Include a concise subject and relevant details, then request confirmation before creating the commit.

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

• Draft a message for staged changes
• Use a consistent commit message format
• Document the purpose of a change

Create a GitHub pull request from the current branch with a structured title, a clear explanation of behavior changes, and recorded check results. For UI changes, attach before-and-after screenshots so reviewers can assess the visual differences.

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

• Preparing and publishing a PR from the current branch
• Writing a PR description backed by verification results
• Attaching before-and-after screenshots for UI changes

Review a branch's commits, combine adjacent changes that belong together, and improve commit messages. A rebuilt history is prepared separately and replaces the original branch only after the user reviews and confirms the proposed changes.

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

• Combining unpushed commits on the current branch
• Cleaning up a named branch without checking it out
• Improving unclear commit messages

Write a human changelog from the REAL commit history — read the actual commit range via the GitHub connector, not a template. Use when asked to write the changelog for this release, what changed since the last tag, draft release notes from my commits, or summarise this range for users in Cowork. Reads commits/PRs between two refs via the GitHub connector, groups them into user-facing changes (features / fixes / breaking), translates commit-speak into human benefit, and produces a changelog artifact ready for the release.

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

Canonical rules for writing git commits in the Shift codebase. Use whenever the user asks to commit, stage and commit, create a pull request that requires commits, or draft a commit message. Enforces Conventional Commits, release-note quality, concise subjects, and logical commit boundaries.

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

Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software evolution, conducting empirical studies on defect prediction, or reducing false positives in bug localization. Supports git repositories and provides explanations for why commits are identified as bug-introducing.

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

Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's commits follow (or mostly follow) Conventional Commits and a mechanically-accurate section breakdown beats a model's reading of the diff.

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

Cria automaticamente changelogs voltados para usuários a partir de commits do git, analisando o histórico de commits, categorizando mudanças e transformando commits técnicos em notas de lançamento claras e amigáveis para clientes. Transforma horas de escrita manual de changelog em minutos de geração automatizada.

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

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.

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

Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.

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

커밋 직전에 파일을 정리하고 기존 타입 검사와 테스트를 실행하도록 설정합니다. Husky와 lint-staged의 설치부터 설정 파일 작성과 동작 확인까지 다룹니다.

• 커밋 전 자동 검사 도입
• Prettier로 커밋 대상 파일 정리
• 기존 타입 검사와 테스트 실행

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

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