메뉴
Generate a JIRA-linked conventional commit message from staged git changes. Extracts ticket number from branch name (PRO-####, BUG-###), checks for new TODO comments, formats the message, and copies it to clipboard via pbcopy. Does not commit — output only.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/aaronmaturen/pi-config --skill commit-msg명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Investigate a technical spike by gathering requirements interactively, analyzing the codebase with grep and read tools, researching libraries and technologies, evaluating options, and producing a structured report with a high-level proposals doc (for managers/PMs/designers) and detailed technical analysis. Uses Monte Carlo simulation for timeline forecasting with confidence levels. Optionally integrates with JIRA if a ticket ID is referenced.
Investigate a bug using the 5 Whys root cause analysis technique. Fetches ticket details from JIRA (if a ticket ID is provided), checks for previous investigation reports, defines Fix Verification Criteria before digging in, traces the bug across frontend and backend repos, and generates a structured investigation report with timeline and recommendations. Requires jira CLI if using a ticket ID.
Investigate and plan implementation of a new feature using Acceptance Criteria as the central organizing principle. Fetches ticket details from JIRA, validates and clarifies AC before any planning begins, maps every implementation task back to a specific AC, and generates an implementation plan, technical design, task breakdown, and PR checklist template. Requires jira CLI.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | commit-msg |
| description | Generate a JIRA-linked conventional commit message from staged git changes. Extracts ticket number from branch name (PRO-####, BUG-###), checks for new TODO comments, formats the message, and copies it to clipboard via pbcopy. Does not commit — output only. |
Analyze staged changes and generate a commit message with JIRA ticket number from the current branch.
IMPORTANT:
Extract ticket number from branch
git branch --show-current to get current branch namePRO-#### (e.g., PRO-1234)BUG-### (e.g., BUG-123)Analyze staged changes
git diff --cached to see only staged changesgit diff to see all unstaged changesgit status --short to see all modified/new filesgit diff --cached --stat to see what files will be committedgit branch --show-currentgit log --oneline main..HEAD (if main exists)Check for new TODO comments
git diff --cached to scan staged changes for new TODO commentsTODO:TODO(// TODO# TODO/* TODOGenerate commit message format:
[PRO-####] Brief description (50 chars total)
Detailed explanation of changes, why they were made,
and any important context. Wrap at 72 characters.
If no ticket number found, use format:
Brief description (50 chars max)
Detailed explanation of changes, why they were made,
and any important context. Wrap at 72 characters.
Copy to clipboard:
pbcopy to copy it to clipboard[PRO-####] or [BUG-###], 50 chars max totalWith PRO ticket:
[PRO-1234] Add user authentication flow
Implemented login and registration endpoints with JWT tokens.
Added password reset functionality and email verification
to ensure secure user onboarding.
With BUG ticket:
[BUG-567] Fix memory leak in image processor
Properly dispose of image buffers after processing.
Added cleanup in finally block to ensure resources
are released even on exceptions.
Without ticket (normal branch):
Refactor database connection pooling
Extracted connection logic into separate module for
better testability and reuse across services.