메뉴
Commit all working-tree and untracked changes in git using an automatically generated Conventional Commit message.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Review recent code changes and broad codebase areas for critical and high severity security vulnerabilities. Use when Codex needs to clear `./out-security-review`, select 25 non-doc, non-test files split across past-day commits, past-week commits, and broad codebase coverage, group them into 6-8 review buckets, spawn one security-review sub-agent per review bucket, persist each candidate finding to `./out-security-review/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for responsible disclosure.
Record a short Playwright-based product demo video for significant UI or user-visible functionality changes. Use when Codex needs to show a workflow in motion for a PR, either by recording an existing targeted E2E spec or by creating a disposable one-off Playwright spec that captures the changed behavior in under a minute, then uploading the final video to Vercel Blob and preparing a PR comment body that says "Demo at commit {hash}" with a 1-2 sentence summary and durable hosted link.
Review the last 7 days of recent commits for large architecture improvements that dramatically improve maintainability. Use when the agent needs to clear `./out-code-architect`, select 25 non-doc, non-test files from recent commits across different parts of the repo, spawn one architecture-review sub-agent per starting file, persist each candidate finding to `./out-code-architect/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for issue filing.
Review the last 7 days of recent commits for critical and high severity bugs that break user experience. Use when the agent needs to clear `./out-bug-finder`, select 25 non-doc, non-test files from recent commits across different parts of the repo, spawn one bug-review sub-agent per starting file, persist each candidate finding to `./out-bug-finder/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for issue filing.
Review recent GitHub Actions workflow runs, separate expected noise from actionable failures, and write a machine-readable workflow health report for deterministic post-agent issue handling.
Print the full host-side `scripts/pr.sh` command needed to create or switch to a feature branch, commit current changes, push, and open or update a PR outside the Docker sandbox using explicit flag-style inputs.
| name | commit |
| description | Commit all working-tree and untracked changes in git using an automatically generated Conventional Commit message. |
Use this skill when the user asks for a one-step git commit of current changes.
git add -A) and stop if there is nothing to commit.git diff --cached --stat
git diff --cached
bash .agents/skills/commit/scripts/commit.sh "<message>"
--no-verify to bypass hooks.Format: type(scope): subject
Type — choose based on the semantic intent of the changes:
feat — new feature or capabilityfix — bug fixrefactor — restructuring without behavior changedocs — documentation onlytest — adding or updating testschore — maintenance, deps, configci — CI/CD pipeline changesperf — performance improvementstyle — formatting, whitespace (no logic change)Scope — a short token identifying the area of the codebase affected (e.g. auth, dashboard, convex, mcp, billing). Use the most specific meaningful scope, not just the top-level directory.
Subject — a concise imperative description of what the change does and why it matters. Be specific and meaningful. Bad: "update 5 files". Good: "add rate limiting to webhook endpoint".
Multi-line body — for larger changes, add a blank line after the subject and include a body explaining the motivation and key details. Use git commit -m "subject" -m "body" format when passing to the script.
Examples of good messages:
feat(auth): add OAuth2 PKCE flow for ChatGPT providerfix(mcp): handle missing tool annotations in protocol responserefactor(billing): extract subscription tier logic into shared helpertest(e2e): add settings page dark mode screenshot testschore(deps): bump convex to 1.17.2