القائمة
Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Turn the current conversation context into a Product Requirements Document (PRD) and submit it as a GitHub issue. Use when the user wants to create a PRD from the current context, or invokes `/create-prd`.
An extremely strict maintainability audit for abstraction quality, giant files, and spaghetti-condition growth. Use for a deep code quality review, code quality audit, or harsh maintainability review.
Write clean, modular bash scripts with proper error handling. Triggers on 'write a script', 'bash script', 'shell script', or 'automate with bash'.
| name | commit-guidelines |
| description | Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits. |
| user-invocable | false |
git log shows the repo follows a different conventionadd, not added/adds)Format: <type>: <summary>
Types:
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
chore | Maintenance tasks, dependencies, config |
refactor | Refactoring (no behavior change) |
perf | Performance improvement |
docs | Documentation only |
test | Test additions or corrections |
style | Code formatting (no logic change) |
Skip the body when the subject is self-explanatory. Add a body only for:
Wrap body text at 72 characters.
Append ! after the type and add a BREAKING CHANGE: footer:
feat!: remove deprecated v1 endpoints
BREAKING CHANGE: v1 endpoints no longer available
Reference GitHub issues in the commit footer:
Fixes #123 — closes the issue when mergedRefs #123 — links without closingfeat: add OAuth2 login flow
fix: handle null response in user endpoint
The API could return null for deleted accounts, causing a crash.
Fixes #42
refactor: extract validation logic to shared module