القائمة
Follow project commit conventions when preparing commit messages and creating commits. Use when drafting, reviewing, or validating commit messages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Fetch and understand documentation for a library or dependency before working with it. Use this skill whenever a library, package, or framework is mentioned that requires understanding its API, usage, or current version behavior.
Organize or refactor modern TypeScript backends with clear module boundaries, readable files, practical reuse, high cohesion, low coupling, and explicit public exports. Use when shaping backend folder structure, splitting responsibilities inside modules, deciding what belongs in `modules/`, `services/`, or `lib/`, or cleaning up layer-based sprawl.
| name | commit-conventions |
| description | Follow project commit conventions when preparing commit messages and creating commits. Use when drafting, reviewing, or validating commit messages. |
All commits must follow the Conventional Commits specification v1.0.0.
Format:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Allowed types:
feat - a new featurefix - a bug fixdocs - documentation changes onlystyle - formatting, missing semicolons, etc; no logic changerefactor - code change that is neither a fix nor a featuretest - adding or updating testschore - build process, tooling, dependency updatesci - CI/CD configuration changesperf - performance improvementsrevert - reverting a previous commitRules:
After making a commit, ask whether I would like to push the changes to the upstream branch.