Skip to content

aiskillstore/marketplace / skills/21pounder/git-commit

git-commit

Verified

Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

FileKindSize
SKILL.mdskill md2.6 KB
skill-report.jsonconfig14.1 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-04T16:37:14.269Z",
    "slug": "21pounder-git-commit",
    "source_url": "https://github.com/21pounder/terminalAgent/tree/main/deepresearch/.claude/skills/git-commit",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "7382718fb5817ffb97f580e1f3ceae80e9179cc6fd1470f1dbb38298eaf1a8df",
    "tree_hash": "1e3f3817e9999da5888e2834a3db8bdbce78c7d3ae973b9d8c5134af05d36921",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "git-commit",
    "description": "Guides git status review, change analysis, staging, and conventional commit creation for repository work.",
    "summary": "Create structured git commits from staged or unstaged repository changes.",
    "icon": "πŸ“¦",
    "version": "1.0.1",
    "author": "21pounder",
    "license": "MIT",
    "category": "coding",
    "tags": [
      "git",
      "commits",
      "conventional-commits",
      "version-control",
      "workflow"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "external_commands"
    ]
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "The static findings are false positives caused by Markdown code fences and inline command examples, not executable Ruby backtick calls. The skill uses expected git commands for commit workflow guidance and explicitly warns users not to commit sensitive files.",
    "remediation": [],
    "risk_factor_evidence": [
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 14,
            "line_end": 34
          },
          {
            "file": "SKILL.md",
            "line_start": 34,
            "line_end": 46
          },
          {
            "file": "SKILL.md",
            "line_start": 46,
            "line_end": 47
          },
          {
            "file": "SKILL.md",
            "line_start": 47,
            "line_end": 48
          },
          {
            "file": "SKILL.md",
            "line_start": 48,
            "line_end": 61
          },
          {
            "file": "SKILL.md",
            "line_start": 61,
            "line_end": 71
          },
          {
            "file": "SKILL.md",
            "line_start": 71,
            "line_end": 85
          },
          {
            "file": "SKILL.md",
            "line_start": 85,
            "line_end": 85
          }
        ]
      }
    ],
    "static_findings": [
      {
        "id": "external_commands:SKILL.md:14:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 14,
        "line_end": 34,
        "snippet": "```json"
      },
      {
        "id": "external_commands:SKILL.md:34:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 34,
        "line_end": 46,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:46:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 46,
        "line_end": 47,
        "snippet": "- Run `git status` to see current state"
      },
      {
        "id": "external_commands:SKILL.md:47:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 47,
        "line_end": 48,
        "snippet": "- Run `git diff --staged` to see staged changes"
      },
      {
        "id": "external_commands:SKILL.md:48:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 48,
        "line_end": 61,
        "snippet": "- Run `git diff` to see unstaged changes"
      },
      {
        "id": "external_commands:SKILL.md:61:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 61,
        "line_end": 71,
        "snippet": "- Verify success with `git status`"
      },
      {
        "id": "external_commands:SKILL.md:71:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 71,
        "line_end": 85,
        "snippet": "- Follow Conventional Commits format: `type(scope): description`"
      },
      {
        "id": "external_commands:SKILL.md:85:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 85,
        "line_end": 85,
        "snippet": "1. Run `git status` and `git diff` to understand changes"
      },
      {
        "id": "sensitive:SKILL.md:74:environment-file-access",
        "category": "sensitive",
        "severity": "high",
        "pattern": "Environment file access",
        "file": "SKILL.md",
        "line_start": 74,
        "line_end": 74,
        "snippet": "- Don't commit sensitive files (.env, credentials, etc.)"
      }
    ],
    "finding_verdicts": [
      {
        "id": "external_commands:SKILL.md:14:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 14 starts a Markdown json code fence for parameter documentation. It is not Ruby backtick execution and does not run a shell command."
      },
      {
        "id": "external_commands:SKILL.md:34:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 34 closes a Markdown code fence. It is documentation syntax, not executable shell or Ruby code."
      },
      {
        "id": "external_commands:SKILL.md:46:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.92,
        "reason": "The inline text documents running git status as part of a git commit workflow. This is an expected read-only repository command, not shell backtick execution."
      },
      {
        "id": "external_commands:SKILL.md:47:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.92,
        "reason": "The inline text documents git diff --staged for inspecting staged changes. It is an expected read-only git command and not an injection pattern."
      },
      {
        "id": "external_commands:SKILL.md:48:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.92,
        "reason": "The inline text documents git diff for reviewing unstaged changes. It is normal git workflow guidance and does not execute user-controlled shell code."
      },
      {
        "id": "external_commands:SKILL.md:61:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.91,
        "reason": "The inline text recommends git status after commit creation. This is a benign verification step in the stated git workflow."
      },
      {
        "id": "external_commands:SKILL.md:71:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "The inline backticks wrap a Conventional Commits message format example. It is not a command and has no execution behavior."
      },
      {
        "id": "external_commands:SKILL.md:85:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.92,
        "reason": "The text describes running git status and git diff to understand changes. These are expected read-only git commands for this skill's purpose."
      },
      {
        "id": "sensitive:SKILL.md:74:environment-file-access",
        "verdict": "false_positive",
        "confidence": 0.96,
        "reason": "The line says not to commit sensitive files such as .env or credentials. It is protective guidance, not access to environment files."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 100,
    "audit_model": "codex",
    "audited_at": "2026-07-04T16:37:14.269Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Create Conventional Git Commits",
    "value_statement": "Manual commit preparation can miss staged changes, message style, or sensitive files. This skill reviews git state and helps create clear conventional commits.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "git commit",
      "conventional commits",
      "version control",
      "commit message",
      "staged changes",
      "developer workflow",
      "repository automation"
    ],
    "actual_capabilities": [
      "Checks repository status before creating a commit.",
      "Reviews staged and unstaged changes with git diff commands.",
      "Suggests a Conventional Commits type, scope, and description.",
      "Stages relevant files when the user wants a full commit workflow.",
      "Creates the commit and reports the resulting commit hash.",
      "Warns against committing sensitive files such as credentials."
    ],
    "limitations": [
      "Requires a local git repository with command-line access.",
      "Does not push commits to a remote repository.",
      "Does not rewrite history unless the user explicitly requests it.",
      "Commit quality depends on readable diffs and clear project context."
    ],
    "use_cases": [
      {
        "title": "Prepare Feature Commits",
        "description": "Turn implementation changes into a concise feature commit with a conventional message.",
        "target_user": "Application developers"
      },
      {
        "title": "Standardize Team History",
        "description": "Apply consistent commit types and scopes before opening a pull request.",
        "target_user": "Engineering teams"
      },
      {
        "title": "Commit Documentation Updates",
        "description": "Review documentation diffs and create a focused docs commit.",
        "target_user": "Technical writers"
      }
    ],
    "prompt_templates": [
      {
        "title": "Commit My Changes",
        "prompt": "Commit my current changes with an appropriate conventional commit message.",
        "scenario": "Beginner workflow for a standard repository commit."
      },
      {
        "title": "Use a Specific Type",
        "prompt": "Create a fix commit for the current changes and choose a suitable scope.",
        "scenario": "User already knows the intended commit type."
      },
      {
        "title": "Review Before Commit",
        "prompt": "Review the staged and unstaged changes, explain the commit plan, then create the commit.",
        "scenario": "User wants confirmation before modifying git history."
      },
      {
        "title": "Split Mixed Changes",
        "prompt": "Analyze my working tree and suggest separate conventional commits before staging anything.",
        "scenario": "Advanced workflow for mixed or multi-area changes."
      }
    ],
    "output_examples": [
      {
        "input": "Commit my changes.",
        "output": "Created commit feat(auth): add password reset flow. Included the auth form, API handler, and related tests."
      },
      {
        "input": "Make this a docs commit.",
        "output": "Created commit docs(readme): clarify setup steps. The commit contains only documentation updates."
      },
      {
        "input": "Review changes before committing.",
        "output": [
          "Found staged updates in the payment module and unstaged test changes.",
          "Recommended splitting them into fix(payment) and test(payment) commits."
        ]
      }
    ],
    "best_practices": [
      "Review git status and diffs before allowing the commit.",
      "Keep commits focused on one logical change.",
      "Confirm sensitive files are excluded before staging."
    ],
    "anti_patterns": [
      "Committing unrelated changes into one large commit.",
      "Using vague messages such as update or changes.",
      "Committing secrets, local configuration, or generated files by accident."
    ],
    "faq": [
      {
        "question": "Does this skill push commits to a remote?",
        "answer": "No. It focuses on local commit creation and status reporting."
      },
      {
        "question": "Can it use Conventional Commits?",
        "answer": "Yes. It is designed to choose conventional types, scopes, and concise descriptions."
      },
      {
        "question": "Will it stage files automatically?",
        "answer": "It can stage relevant files when the workflow requires it and the user allows it."
      },
      {
        "question": "Does it protect secrets?",
        "answer": "It includes guidance to avoid committing .env files, credentials, and other sensitive files."
      },
      {
        "question": "Can it split changes into multiple commits?",
        "answer": "It can analyze mixed changes and suggest separate commits before staging."
      },
      {
        "question": "Which tools can use this skill?",
        "answer": "The report lists support for Claude, Codex, and Claude Code."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 100
    }
  ]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why β€” repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" β€” or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself β€” your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall