بنقرة واحدة
git-commit
Create a well-formatted git commit with conventional commit message format and ticket reference
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create a well-formatted git commit with conventional commit message format and ticket reference
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Find a git branch by Linear ticket ID prefix (e.g., STU-15)
Create or reuse a dedicated git worktree for a branch using a deterministic path layout
Create and maintain implementation progress documentation for a feature branch
Find the worktree path for a branch and create/reuse it when missing
Resolve a properly named git branch from a Linear ticket ID following the convention {type}/{ticket-id}-short-description
Push the current branch to the remote repository with upstream tracking
استنادا إلى تصنيف SOC المهني
| name | git-commit |
| description | Create a well-formatted git commit with conventional commit message format and ticket reference |
Create a git commit following the conventional commits specification with Linear ticket reference.
{type}({scope}): {description}
{body}
Refs: {ticket-id}
| Type | Description |
|---|---|
feat | New feature |
fix | Bug fix |
refactor | Code refactoring |
docs | Documentation only |
test | Adding/updating tests |
chore | Maintenance, deps, tooling |
perf | Performance improvement |
style | Code style (formatting, semicolons) |
ci | CI/CD changes |
Optional, indicates the component affected:
api - Backend API changesmobile - Mobile app changesinfra - Infrastructure/Terraform changesshared - Shared libraries/utilitiesGet authenticated identity for commit attribution (recommended):
get_authenticated_user tool (GitHub App) or get_me tool (PAT/official MCP)name and email) to use for commitsStage changes:
git add -A
Or stage specific files if making focused commits:
git add path/to/file1 path/to/file2
Review staged changes:
git diff --staged --stat
Create commit:
If authenticated identity was retrieved, use environment variables to set both author and committer:
GIT_AUTHOR_NAME="{name}" GIT_AUTHOR_EMAIL="{email}" GIT_COMMITTER_NAME="{name}" GIT_COMMITTER_EMAIL="{email}" git commit -m "{type}({scope}): {description}" -m "{body}" -m "Refs: {ticket-id}"
Example with bot identity:
GIT_AUTHOR_NAME="my-app[bot]" GIT_AUTHOR_EMAIL="123456+my-app[bot]@users.noreply.github.com" GIT_COMMITTER_NAME="my-app[bot]" GIT_COMMITTER_EMAIL="123456+my-app[bot]@users.noreply.github.com" git commit -m "feat(api): add endpoint" -m "Add new endpoint for user authentication" -m "Refs: STU-15"
If no authenticated identity (fallback), use standard commit:
git commit -m "{type}({scope}): {description}" -m "{body}" -m "Refs: {ticket-id}"
feat(api): add user authentication endpoint
Implement JWT-based authentication with refresh tokens.
Includes rate limiting and brute force protection.
Refs: STU-15
fix(mobile): resolve login timeout issue
Increase timeout from 5s to 30s for slow networks.
Add retry logic with exponential backoff.
Refs: STU-23
test(api): add integration tests for auth endpoints
Cover login, logout, and token refresh flows.
Add edge cases for invalid credentials.
Refs: STU-15
Before committing:
After committing:
git log -1 --oneline
Report the commit hash to confirm success.