aiskillstore/marketplace / skills/5t111111/git-operation
git-operation
VerifiedGuide for basic Git operations
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 676 B |
| skill-report.json | config | 9.1 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-04T16:59:49.406Z",
"slug": "5t111111-git-operation",
"source_url": "https://github.com/5t111111/tailwind-theme-figma-variables/tree/main/.github/skills/git-operation",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "ce13e7287fe106f83a4a6f6010fd04fdabead4a35f686f4ac23fa79f613b7e48",
"tree_hash": "f7230e3c4fd2965eea0864f6407b93d3e368facb370b52315adcb2959fbd667e",
"provenance": {
"model_effective": "codex",
"fallback_chain": [
{
"agent": "codex",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "git-operation",
"description": "Guide for writing consistent Git commit messages and running project checks before committing code changes.",
"summary": "Prepare clear Git commits with message structure, formatting, and test guidance.",
"icon": "📦",
"version": "1.0.1",
"author": "5t111111",
"license": "MIT",
"tags": [
"git",
"commits",
"formatting",
"testing",
"developer-workflow"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"external_commands"
],
"category": "devops"
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "The two static findings are false positives caused by Markdown inline command examples, not Ruby or shell backtick execution. The skill is prompt-only and contains no prompt injection, data exfiltration, or hidden automation.",
"remediation": [],
"risk_factor_evidence": [
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 18,
"line_end": 18
},
{
"file": "SKILL.md",
"line_start": 19,
"line_end": 19
}
]
}
],
"static_findings": [
{
"id": "external_commands:SKILL.md:18:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 18,
"line_end": 18,
"snippet": "- Always run `mise run fmt` to format the code before committing"
},
{
"id": "external_commands:SKILL.md:19:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 19,
"line_end": 19,
"snippet": "- Always run `mise run test` before committing code changes to ensure no tests"
}
],
"finding_verdicts": [
{
"id": "external_commands:SKILL.md:18:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.92,
"reason": "Line 18 uses Markdown inline code to name a local format check, not Ruby or shell backtick execution. The command is visible guidance for commit preparation and is not dynamically constructed."
},
{
"id": "external_commands:SKILL.md:19:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.92,
"reason": "Line 19 uses Markdown inline code to name a local test check, not Ruby or shell backtick execution. The command is visible guidance for commit preparation and is not hidden automation."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 1,
"total_lines": 21,
"audit_model": "codex",
"audited_at": "2026-07-04T16:59:49.406Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Write Clear Git Commits",
"value_statement": "Teams need consistent commits and checks before code lands. This skill guides commit message structure, formatting, and test steps for Claude, Codex, and Claude Code.",
"seo_keywords": [
"Git commit skill",
"Claude",
"Codex",
"Claude Code",
"commit message guide",
"Git operations",
"mise format test",
"code review workflow",
"developer productivity",
"AI coding assistant"
],
"actual_capabilities": [
"Guides English Git commit messages with concise first lines.",
"Explains when to add a blank line and bullet details.",
"Instructs agents to run mise format checks before committing.",
"Instructs agents to run mise test checks before committing code changes.",
"Focuses on commit preparation, not full Git workflow automation."
],
"limitations": [
"Does not define branch creation, merge, rebase, or release workflows.",
"Assumes the repository supports mise tasks named fmt and test.",
"Does not run Git commands by itself; the host agent executes requested steps.",
"Does not explain project-specific commit scopes or issue references."
],
"use_cases": [
{
"title": "Prepare Consistent Commits",
"description": "Use the skill to write English commit summaries and verify formatting before committing.",
"target_user": "Solo developers"
},
{
"title": "Standardize Team Commit Quality",
"description": "Apply shared commit message structure and pre-commit checks across assistant-supported changes.",
"target_user": "Engineering teams"
},
{
"title": "Review Agent Changes Before Commit",
"description": "Ask an AI assistant to summarize edits, run checks, and produce a clear commit message.",
"target_user": "Technical leads"
}
],
"prompt_templates": [
{
"title": "Draft a Commit Message",
"prompt": "Create an English Git commit message for the current changes. Use a concise first line and add bullet details only if needed.",
"scenario": "Beginner commit drafting"
},
{
"title": "Run Pre-Commit Checks",
"prompt": "Review my current changes, run the configured format and test checks, then suggest a commit message.",
"scenario": "Basic commit preparation"
},
{
"title": "Prepare Staged Changes",
"prompt": "Inspect the staged changes, explain the user-facing impact, and draft a commit message with a short subject and optional bullets.",
"scenario": "Intermediate staged review"
},
{
"title": "Plan Clean Commits",
"prompt": "Analyze staged and unstaged changes separately, identify unrelated work, recommend a clean commit plan, run checks, and draft final messages.",
"scenario": "Advanced multi-change review"
}
],
"output_examples": [
{
"input": "I changed button spacing and fixed a validation message.",
"output": "Subject: Improve button spacing and validation copy. Details mention layout polish and clearer form feedback."
},
{
"input": "The assistant prepared a commit after a small refactor.",
"output": "It reports that formatting passed, tests passed, and the commit message is ready in English."
},
{
"input": "Several unrelated files changed during one work session.",
"output": "It recommends separating documentation edits from source changes before committing."
}
],
"best_practices": [
"Stage only related changes before asking for a commit message.",
"Run the project format and test tasks before creating the commit.",
"Keep the first commit line short and written in English."
],
"anti_patterns": [
"Do not combine unrelated changes in one commit.",
"Do not skip checks when source files changed.",
"Do not use long paragraphs in the commit subject."
],
"faq": [
{
"question": "Does this skill run commands automatically?",
"answer": "No. It tells the host agent which checks to run when preparing a commit."
},
{
"question": "Which tools does it support?",
"answer": "It supports Claude, Codex, and Claude Code through prompt instructions."
},
{
"question": "Does it require mise?",
"answer": "The guidance assumes mise tasks are available. Projects without those tasks need equivalent local commands."
},
{
"question": "Can it create branches?",
"answer": "No. The skill focuses on commit preparation and message guidance."
},
{
"question": "Can it write non-English messages?",
"answer": "The skill requires English commit messages."
},
{
"question": "Is it safe for private repositories?",
"answer": "It does not request network access or secrets. Review any local checks before running them."
}
]
},
"file_structure": [
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 21
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |