القائمة
Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose software failures through reproduction, boundary localization, competing hypotheses, and discriminating experiments. Use when Codex is asked to investigate a bug, flaky test, crash, incorrect result, performance regression, production symptom, or unexplained behavior and should determine the cause before implementing a fix. Produce an evidence-backed causal explanation and verification plan; do not patch unless the user also asks for a fix.
Design, implement, or review compatible and reversible database, event, API payload, configuration, or persisted-data schema evolution. Use for migrations, column or field changes, backfills, constraint changes, data transformations, serialization upgrades, zero-downtime deploys, or rollback planning where old and new code or data may coexist. Require explicit expand-migrate-contract sequencing, data invariants, operational bounds, and recovery evidence.
Audit an AI agent harness for production readiness from repository code, configuration, tests, and run traces. Score 44 runtime controls across eight outcomes with artifact evidence, identify audit limitations, assign an evidenced maturity band, make a launch decision, and produce a dependency- ordered fix queue. Use for agent safety, governance, ship-readiness, control- gap, or due-diligence reviews of LangGraph, OpenAI Agents SDK, Google ADK, CrewAI, multi-agent, MCP-enabled, or custom agent systems. Do not use as a questionnaire or as a substitute for a runtime penetration test.
Produce an implementation-ready plan for a software change by inspecting the actual repository, tracing affected execution paths, resolving material design decisions, and defining verification and rollout evidence. Use when the user asks for an implementation plan, technical approach, task breakdown, design proposal grounded in an existing codebase, or wants to know how a feature or fix should be built before editing begins. Do not use for generic product roadmaps or when the user has asked to implement immediately.
Restructure existing code while preserving externally observable behavior through explicit invariants, characterization evidence, small reversible steps, and continuous verification. Use when the user asks to refactor, simplify, extract, reorganize, modularize, deduplicate, split a component, improve architecture, or pay down technical debt without intentionally changing product behavior. Distinguish refactoring from feature work and stop scope drift from hiding inside structural edits.
Map an unfamiliar software repository from code and configuration. Use when Codex needs to understand a new codebase, locate entry points or ownership boundaries, explain architecture and runtime flow, identify where a change belongs, or prepare for implementation without yet modifying files. Produce an evidence-backed repository map, not a directory listing or README paraphrase.
| name | commit-message |
| description | Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed. |
Generate a high-quality commit message that describes the staged changes.
git diff --staged to see what is actually being committed. If nothing
is staged, inspect git status and ask the user what to stage.<type>(<optional scope>): <subject>
<body — what changed and why, wrapped at ~72 cols>
feat, fix, refactor, docs, test, chore, perf,
build, ci.feat(auth): add refresh-token rotation
Tokens are now rotated on every refresh so a leaked token is valid for
at most one cycle.
fix(parser): handle empty input without panicking