본문으로 건너뛰기
cccskills
무료GitHub에 공개

commit

Create a Git commit from current changes using the session history to explain their purpose. The skill checks which files belong, stages the intended work, and writes a structured message covering changes, rationale, and validation.

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

원문원문 설명 보기

Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.

openai/symphony
설치 방법 보기

이럴 때 유용합니다

  • Commit completed work with its rationale
  • Draft a commit message from the session history
  • Check staged files for unrelated changes
  • Record validation results in a commit message

포함된 파일(1)

  • SKILL.md2.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Commit

Goals

  • Produce a commit that reflects the actual code changes and the session context.
  • Follow common git conventions (type prefix, short subject, wrapped body).
  • Include both summary and rationale in the body.

Inputs

  • Codex session history for intent and rationale.
  • git status, git diff, and git diff --staged for actual changes.
  • Repo-specific commit conventions if documented.

Steps

  1. Read session history to identify scope, intent, and rationale.
  2. Inspect the working tree and staged changes (git status, git diff, git diff --staged).
  3. Stage intended changes, including new files (git add -A) after confirming scope.
  4. Sanity-check newly added files; if anything looks random or likely ignored (build artifacts, logs, temp files), flag it to the user before committing.
  5. If staging is incomplete or includes unrelated files, fix the index or ask for confirmation.
  6. Choose a conventional type and optional scope that match the change (e.g., feat(scope): ..., fix(scope): ..., refactor(scope): ...).
  7. Write a subject line in imperative mood, <= 72 characters, no trailing period.
  8. Write a body that includes:
    • Summary of key changes (what changed).
    • Rationale and trade-offs (why it changed).
    • Tests or validation run (or explicit note if not run).
  9. Append a Co-authored-by trailer for Codex using Codex <codex@openai.com> unless the user explicitly requests a different identity.
  10. Wrap body lines at 72 characters.
  11. Create the commit message with a here-doc or temp file and use git commit -F <file> so newlines are literal (avoid -m with \n).
  12. Commit only when the message matches the staged changes: if the staged diff includes unrelated files or the message describes work that isn't staged, fix the index or revise the message before committing.

Output

  • A single commit created with git commit whose message reflects the session.

Template

Type and scope are examples only; adjust to fit the repo and changes.

<type>(<scope>): <short summary>

Summary:
- <what changed>
- <what changed>

Rationale:
- <why>
- <why>

Tests:
- <command or "not run (reason)">

Co-authored-by: Codex <codex@openai.com>

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

debug

무료

Investigate stalled, retrying, or failed Symphony runs by connecting Linear issue identifiers with Codex sessions. Trace log events in time order, identify the failing stage, and collect evidence for the probable cause.

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

  • Investigate a stalled run
  • Trace repeated retries
  • Identify where a Codex session failed
openai/symphony2.8만2026년 9월 16일 업데이트

land

무료

Guide a pull request through conflict resolution, review feedback, and automated checks. The skill monitors progress, fixes failures, and completes a squash merge, combining the branch’s changes into one commit once checks and reviews are addressed.

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

  • Follow a pull request through to its merge
  • Resolve conflicts with main before merging
  • Investigate failed automated checks and rerun them
openai/symphony2.8만2026년 9월 16일 업데이트

linear

무료

Work with Linear issues through Symphony’s authenticated client. Retrieve issue details, update workflow states, create or edit comments, link GitHub pull requests, and upload videos using GraphQL, an API language for requesting specific data.

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

  • Retrieve Linear issue details
  • Create or edit issue comments
  • Change an issue's workflow state
openai/symphony2.8만2026년 9월 16일 업데이트

pull

무료

Update a working Git branch with the latest origin/main through a merge. The skill checks branch state, resolves conflicting edits with attention to both changes’ intent, runs project checks, and summarizes the resolution.

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

  • Bring the latest main changes into a feature branch
  • Resolve conflicts while preserving both changes’ intent
  • Sync remote feature branch updates before merging
openai/symphony2.8만2026년 9월 16일 업데이트

push

무료

Publish the current Git branch to origin and create or update its pull request, a request to review and merge changes. The skill runs validation and refreshes the title and description to match the full scope.

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

  • Publish local branch changes to origin
  • Create a pull request using the project template
  • Refresh a pull request after its scope changes
openai/symphony2.8만2026년 9월 16일 업데이트

release

무료

Prepare a Symphony release by updating its version, running checks, merging the change, and tagging the merged commit. Then monitor the Burrito release workflow and verify that the GitHub release contains the expected assets.

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

  • Release a specified Symphony version
  • Prepare the next patch release
  • Tag the merged release commit
openai/symphony2.8만2026년 9월 16일 업데이트

openai의 스킬 모두 보기

이 스킬의 문제 신고