القائمة
Git commit workflow and standards. Use when committing code, batching changes, or verifying builds before commits. Covers build verification, commit message format, and quality gates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Backend API development with Express, Zod validation, permissions, and security. Use when creating or modifying API endpoints, adding route handlers, implementing validation, or working with authentication/authorization.
Query and analyze production logs via BetterStack MCP. Use when diagnosing production issues, investigating errors, analyzing patterns, or monitoring system health.
Code quality standards, complexity management, and anti-over-engineering. Use when reviewing code, implementing features, or ensuring quality standards. Covers complexity limits, linting, and simplicity principles.
Documentation standards and decision criteria. Use when deciding whether to document, creating documentation, or maintaining existing docs. Covers significance thresholds, structure, and cross-referencing.
Debug local development issues by analyzing logs, checking processes, and diagnosing errors. Use when servers won't start, errors occur, or behavior is unexpected.
MCP (Model Context Protocol) tools for code intelligence, refactoring, browser automation, and external integrations. Use cclsp for refactoring, find references, rename symbols. Use Playwright for UI testing. Use GitHub MCP for PR operations.
| name | git-commits |
| description | Git commit workflow and standards. Use when committing code, batching changes, or verifying builds before commits. Covers build verification, commit message format, and quality gates. |
Standards for creating clean, well-organized commits.
BEFORE ANY COMMIT, verify builds pass:
# Frontend
cd frontend && npm run build
# Backend
cd backend && npm run build:typecheck
BUILD FAILURE = NO COMMIT. A broken build means code cannot be deployed.
<type>: <subject> (50 chars max)
<body> (optional, wrap at 72 chars)
- Bullet points for multiple changes
- Focus on WHY, not just WHAT
| Type | Use For |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, no code change |
refactor | Code change, no feature/fix |
test | Adding/updating tests |
chore | Build, deps, config |
# Feature
git commit -m "feat: add company document upload"
# Bug fix
git commit -m "fix: prevent duplicate document names"
# With body
git commit -m "feat: add document type validation
- Added DocumentType enum
- Validate file types on upload
- Return 400 for invalid types"
Each commit should:
Commit 1: feat: add Document database model
Commit 2: feat: add document upload API endpoint
Commit 3: feat: add document list UI component
Commit 4: test: add document management tests
Commit 1: add document feature, fix auth bug, update readme
Commit when you complete:
For multiple commits or complex batching:
Minimize interference from other agents:
# Chain operations to reduce window
git reset HEAD unwanted-file && \
git add wanted-file && \
git commit -m "fix: resolve issue"
NEVER discard changes without explicit user permission.
git restore, git reset --hard, git checkout -- file without askingWhen encountering conflicts or unexpected issues: STOP and ask the user.
If build fails:
# Verify both pass
cd frontend && npm run build && cd ../backend && npm run build:typecheck
# Files with special characters
git add "path/with spaces/file.txt"
# Database changes - ALWAYS together
git add backend/prisma/schema.prisma
git add backend/prisma/migrations/[new_folder]/
git commit -m "feat: add [description] to database"