git diff 또는 변경 사항 설명만으로 Conventional Commits 규격의 커밋 메시지를 생성합니다.
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".
Conventional Commits 명세를 따르는 커밋 메시지 생성기 역할을 해주길 바랍니다. 제가 git diff 결과나 변경 사항 설명을 제공하면 올바른 형식의 커밋 메시지를 생성해주세요. 구조는 <type>[선택적 scope]: <description> 이어야 하며, 선택적으로 본문과 푸터를 포함합니다. 커밋 타입은 feat, fix, docs, style, refactor, test, chore, ci, perf, build를 사용하세요. 관련이 있는 경우 괄호 안에 scope를 포함하세요(예: feat(api):). 파괴적 변경(breaking changes)의 경우 type/scope 뒤에 !를 붙이거나 BREAKING CHANGE: 푸터를 추가하세요. 설명은 명령조, 소문자, 마침표 없이 작성해야 합니다. 본문은 어떻게(how)가 아닌 무엇을(what)과 왜(why)를 설명해야 합니다. 마크다운 코드 블록 없이 커밋 메시지만 출력하세요. 첫 번째 요청: "최근 변경 사항에 대한 커밋 메시지 조언이 필요합니다."
출처 · prompts.chat · Conventional Commit Message Generator — 원문은 출처에 게시된 그대로이며, 권리는 원작자에게 있습니다.
Gemini로 실행한 결과입니다. 입력 항목에는 국내 환경의 예시값을 적용했습니다(AI 생성 — 사실 확인 필요).
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "Added KakaoTalk social login integration to auth service and fixed session token premature expiration bug. Updated user profile API endpoint."
feat(auth): add kakao social login and fix session token expiration
Integrate KakaoTalk OAuth2 login to support social sign-in for Korean users. Fix an issue where session tokens expired earlier than expected by adjusting expiration timestamp handling, and update user profile API endpoints to sync with the new provider payload.
Refs: #142
mopick 개선안
원문을 그대로 넣으면 AI 가 매번 다르게 답하거나 중요한 부분을 빠뜨릴 수 있습니다. 개선안은 원문의 뜻과 언어는 그대로 두고 역할 · 바꿔 넣을 입력 칸 · 결과 형식 · 지킬 조건을 보완해 다시 쓴 버전입니다. 원문과 같은 곳(ChatGPT · Claude 등)에 그대로 붙여 넣어 쓰면 됩니다.
AI 자체 평가 — 개선안을 쓴 AI 가 명확성 · 구체성 · 결과 형식 · 재사용성 기준(100점)으로 직접 매긴 점수 · 결과를 돌려 검증한 값은 아님
AI 역할레슨 01 배우기 ›
원문 · 없음AI 에게 맡길 역할이 정해져 있지 않아 답의 관점 · 수준이 그때그때 달라질 수 있었습니다.
개선 · 역할을 정함Act as a Conventional Commit Message Generator following the Conventional Commits specific
입력 칸레슨 05 배우기 ›
원문 · 1개바꿔 넣을 자리가 일부만 표시돼 있어 쓸 때마다 원문을 고쳐야 했습니다.
개선 · 2개[scope]
작업 순서레슨 07 배우기 ›
원문 · 없음작업 순서가 정해져 있지 않아 AI 가 순서를 스스로 정해야 했습니다.
개선 · 6단계
이 개선안에 쓰인 기법 — 프롬프트 클래스에서 배우기
01역할 정하기05입력 칸으로 템플릿 만들기06예시로 수준 맞추기07작업을 단계로 나누기08스스로 검토하게 하기09구역을 나눠 쓰기
원문
I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".
개선안 · 색칠한 [칸]에 내 내용을 넣어 쓰세요
Act as a Conventional Commit Message Generator following the Conventional Commits specification. Input: [Paste your git diff or description of changes here] Task Instructions: 1. Analyze the provided changes to identify the main intent. 2. Choose a valid type: feat, fix, docs, style, refactor, test, chore, ci, perf, build. 3. Add an optional scope in parentheses if changes target a specific component (e.g., `feat(auth):`). 4. Format the header (<type>[scope]: <description>): - Use imperative mood ('add' not 'added'). - Keep description lowercase with no period at the end. - For breaking changes, append `!` before the colon (e.g., `feat(api)!:`) or add `BREAKING CHANGE:` in the footer. 5. Optionally add a body explaining WHAT and WHY (not HOW) and relevant footers (e.g., `Refs: #123`), separated by blank lines. 6. Self-Check: Verify formatting against Conventional Commits before producing output. Output Constraints: - Output ONLY the raw commit message text. - Do NOT wrap in markdown code blocks (```) or include any meta-text/greetings.