القائمة
Conventional commits format and best practices for writing clear commit messages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | commit-msg |
| description | Conventional commits format and best practices for writing clear commit messages. |
Follow these conventions for clear, useful commit messages.
<type>(<scope>): <description>
[optional body]
[optional footer]
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style (formatting, no logic change)refactor: Code refactoringperf: Performance improvementtest: Adding/updating testschore: Maintenance, dependencies, toolingci: CI configuration changesfeat:, not Feat:feat(auth): add JWT token refresh endpoint
Implements token refresh flow to allow users to obtain new
access tokens without re-authenticating.
Closes #123
fix(api): handle nil response from user service
Returns empty slice instead of nil when no users found.
fix: fixed the thing
Added new feature for user authentication and authorization
with JWT tokens and refresh token support and role-based
access control which allows administrators to manage permissions.
Closes #123 or Fixes #456 to link issuesCloses #123, #456BREAKING CHANGE: descriptionfeat(api)!: change user response format
The user response now includes additional fields. Clients
must be updated to handle the new format.
BREAKING CHANGE: /api/users now returns full User object
instead of just ID and name.
git add -p for selective stagingPython 3.11+ key decisions and patterns. Use when writing Python code.
Rust 2021 edition coding conventions. Use when writing or reviewing Rust code.
TypeScript 5.x / JavaScript ES2022+ coding conventions. Use when writing or reviewing TypeScript/JavaScript code.
Repro-first bug investigation process with root-cause validation and fix planning.
Keep user-facing documentation aligned with current behavior.
Pre-release validation checklist with go/no-go recommendation.