القائمة
Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Provides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, visualizations, or any visual documentation in markdown. Always use this skill when generating or updating Mermaid code blocks.
Documentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
Conduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any subject. Also triggers on "talk me through", "explore X with me", "help me plan Y", or "walk me through my thinking on Z" when the user wants a guided conversation rather than a direct answer. Applies broadly — career decisions, project ideas, product direction, personal goals, research questions, team problems — not just technical topics.
Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".
Provides architectural pattern knowledge for designing feature implementations including MVC, event-driven, microservices, and CQRS patterns. Use when designing system architecture or choosing implementation patterns.
Systematic, hypothesis-driven debugging workflow with triage-based track routing. Use when asked to "fix this bug", "debug this", "why is this failing", "this is broken", "investigate this error", "track down this issue", or any debugging situation. Supports --deep flag to force full investigation.
| name | git-commit |
| description | Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit. |
| dependencies | [] |
Create a commit with a conventional commit message based on staged changes. Automatically stages all changes and analyzes the diff to generate an appropriate commit message.
Execute these steps in order.
Check for changes to commit:
git status --porcelain
Run:
git add .
Report: "Staged all changes."
View the staged diff to understand what changed:
git diff --cached --stat
git diff --cached
Analyze the diff to determine:
Build a conventional commit message following this format:
<type>(<optional-scope>): <description>
[optional body]
Types:
feat - New featurefix - Bug fixdocs - Documentation onlystyle - Formatting, no code changerefactor - Code restructuring without behavior changetest - Adding or updating testschore - Maintenance tasksbuild - Build system or dependenciesci - CI configurationperf - Performance improvementRules:
Run:
git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"
On success:
On pre-commit hook failure:
If the commit fails:
git reset HEAD to unstage without losing changes| Capability | Purpose |
|---|---|
| Shell execution | Run git commands (git status, git add, git diff, git commit, git reset) |
| User interaction | Display commit results, report errors, provide recovery instructions |
git init or cloned)cat <<'EOF') assumes a POSIX-compatible shell (bash, zsh, sh)