메뉴
Create git commits from staged changes. Automatically use when the user asks to commit, make a commit, git commit, save changes, or any variation of committing code. Triggers on requests like "commit this", "commit my changes", "/commit", or "make a commit".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Obsidian vault management suite. Use when the user mentions vault, obsidian, notes, knowledge base, or asks to capture notes, clean up, search, organize, backup, get health reports, or AI-analyze their vault. Handles all vault operations via sub-commands: capture, cleanup, health, search, organize, ai, backup, setup. Triggers on /vault, vault capture, vault cleanup, vault health, vault search, vault organize, vault ai, vault backup, vault setup, or natural language equivalents.
Interactive Stripe subscription lifecycle tester for the ProcurementExpress (po-app) Rails app. Simulates real Stripe webhook flows in dev environment to test subscription lock/unlock behavior. Use when: "test stripe", "test subscription", "test payment flow", "test incomplete subscription", "test payment failed", "test subscription lock", "stripe test scenario", "test billing", "/stripe-subscription-tester", "simulate stripe webhook", "test parent company lock", "test child company cascade", or any request to test Stripe subscription payment flows in the local development environment.
ProcurementExpress approval flow configuration. Use when creating, updating, publishing, or managing approval flows and their steps, conditions, and runs. Approval flows automate the routing of POs and invoices to the right approvers based on configurable conditions. Routes to MCP tools: list_approval_flows, get_approval_flow, create_approval_flow, update_approval_flow, delete_approval_flow, archive_approval_flow, publish_approval_flow, unpublish_approval_flow, list_approval_flow_runs, get_approval_flow_entity, list_approval_flow_versions, get_approval_flow_version_details, rerun_approval_flows. Triggers on: approval flow, approval workflow, approval steps, approval conditions, approval routing, publish flow, flow runs, flow version, flow history, rerun approval.
ProcurementExpress authentication and user profile management. Use when authenticating to the ProcurementExpress API (V1 static token or V3 OAuth2 login), validating or revoking tokens, or managing the current user's profile. Routes to MCP tools: authenticate, validate_token, revoke_token, get_current_user, update_current_user. Triggers on: login, sign in, authenticate, token, session, user profile, my account, change password.
ProcurementExpress budget management. Use when listing, viewing, creating, or updating budgets (cost centers). Routes to MCP tools: list_budgets, get_budget, create_budget, update_budget. Triggers on: budget, cost center, spending limit, budget allocation, remaining budget, budget approvers.
ProcurementExpress company management, employee listing, user invitations, and approver queries. Use when listing companies, switching the active company, viewing company details and settings, managing employees and user invitations, or querying approvers. Routes to MCP tools: list_companies, get_company, get_company_details, set_active_company, list_approvers, list_all_approvers, list_employees, invite_user, get_invite_limit, list_pending_invites, cancel_invite, resend_invite. Triggers on: company, switch company, employees, invite user, approvers, company settings, custom fields, payment terms.
| name | commit |
| description | Create git commits from staged changes. Automatically use when the user asks to commit, make a commit, git commit, save changes, or any variation of committing code. Triggers on requests like "commit this", "commit my changes", "/commit", or "make a commit". |
Generate a clear, concise commit message for my uncommitted changes. You must first spawn a new sub-agent for git tasks. Always use Claude Haiku model for this task.
I need a commit message that follows conventional commit format without emojis, written in a natural, human tone. The message should be informative yet brief, capturing what was done and why when relevant.
Use this structure:
type(scope): #issue_number short descriptive title
- Brief description of what changed
- Why it was changed (if not obvious)
- Any side effects or important notes
Closes #issue_number
feat: New feature or functionalityfix: Bug fix or error correctionperf: Performance improvementsrefactor: Code restructuring without changing functionalitystyle: Formatting, spacing, semicolons (no code change)docs: Documentation updatestest: Adding or updating testschore: Maintenance tasks, dependency updatesbuild: Build system or external dependency changesci: CI/CD configuration changesrevert: Reverting a previous commitfeat(UserProfile):fix(auth):perf(search):docs(README):feat(checkout): #234 add guest checkout option
- Allow users to complete purchase without account
- Store guest orders with email reference
- Add order lookup by email and order ID
Closes #234
fix(api): #456 handle timeout errors in payment gateway
- Catch and retry failed payments up to 3 times
- Show user-friendly error after final attempt
- Log detailed errors for debugging
Closes #456
perf(dashboard): #789 optimize chart rendering
- Implement virtual scrolling for large datasets
- Reduce re-renders using React.memo
- Load data in 5k chunks instead of all at once
Closes #789
refactor(auth): #321 extract validation logic to helpers
- Move email/password validation to separate utils
- Simplify controller methods
- Improve testability of validation rules
Closes #321
To generate the best commit message, provide:
"Generate a commit message for issue #[number] with these changes: [paste diff or describe changes]"
use !git commit the staged changes. VERY IMPORTANT note, don't add unstaged changes, only commit the message. Example, you can only RUN: git commit -m [your generated commit message], you should not run git add command, this is to prevent accidental commit of unwanted files to the git. Big security risk.
ALWAYS print the generated commit message before running the commit command.
REFERENCE: ./skill-rules-fragment.json