القائمة
Create atomic git commits
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user asks for Codex Security workflows: repository-wide or scoped-path security scans, security reviews of pull requests, commits, branch diffs, or working-tree patches, deep exhaustive repository scans, fixing validated or plausible security findings, or individual threat-modeling, finding-discovery, validation, and attack-path-analysis phases.
Clone and inspect external repositories in a reusable local exploration cache. Use this skill when the user asks to explore, inspect, investigate, compare, or answer questions about a repository that may not already be in the current workspace.
Improve test coverage in the OpenAI Agents Python repository: run `bun run coverage`, inspect coverage artifacts, identify low-coverage files, propose high-impact tests, and confirm with the user before writing tests.
Use when diagnosing or fixing runtime CPU spikes, high event-loop latency, memory growth, heap leaks, garbage-collection pressure, or OOM crashes in Node.js, Bun, Deno, JavaScript/TypeScript services, or comparable long-running runtimes. Includes code-first triage, guided CPU and memory profiling, subagent-orchestrated review, before/after profile comparison, and structured remediation reports.
SQLite database optimization, query writing, indexing, and best practices specialist. Proactively analyzes and optimizes SQLite databases for performance and reliability.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
| name | atomic-commit |
| description | Create atomic git commits |
| disable-model-invocation | true |
git statusgit diff HEADgit branch --show-currentgit log --oneline -10Based on the above changes, create atomic git commits.
Commit messages must follow Conventional Commits format:
feat: - new featurefix: - bug fixchore: - maintenance tasksdocs: - documentation changesrefactor: - code refactoringtest: - adding or updating testsRule: Enforce Atomic Git Commits
Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.