Skip to content

aiskillstore/marketplace / skills/89jobrien/git-workflow

git-workflow

Verified

Git workflow and pull request specialist. Use when creating PRs, managing branches, establishing git conventions, or improving code review processes.

FileKindSize
SKILL.mdskill md1.4 KB
references/pull-request.template.mdmarkdown2.8 KB
skill-report.jsonconfig18.4 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-05T12:24:51.805Z",
    "slug": "89jobrien-git-workflow",
    "source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/git-workflow",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "76e35f8bce1e7c8c9343111c02c6df786b39dbba4e1f4ad1b70fdf1f19e4dbe4",
    "tree_hash": "0c6e602e5ee2d6867bd88fc8b556e5aa6e6acc7bf16364e66fe64431ecdeb964",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "git-workflow",
    "description": "Git workflow and pull request specialist. Use when creating PRs, managing branches, establishing git conventions, or improving code review processes.",
    "summary": "Guides Git branch naming, pull request structure, review quality, and merge strategy decisions.",
    "icon": "📦",
    "version": "1.0.2",
    "author": "Joseph OBrien",
    "license": "MIT",
    "category": "devops",
    "tags": [
      "git",
      "pull-requests",
      "branch-management",
      "code-review",
      "developer-workflow"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "external_commands",
      "network"
    ]
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "All static findings were reviewed against the cited files and appear to be false positives in Markdown documentation. The flagged command execution patterns are inline code examples, hardcoded URLs are attribution links, and network reconnaissance hits are checklist text. No prompt injection, data exfiltration intent, or unsafe automation was found.",
    "remediation": [],
    "risk_factor_evidence": [
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "references/pull-request.template.md",
            "line_start": 89,
            "line_end": 90
          },
          {
            "file": "references/pull-request.template.md",
            "line_start": 90,
            "line_end": 96
          },
          {
            "file": "SKILL.md",
            "line_start": 36,
            "line_end": 36
          },
          {
            "file": "SKILL.md",
            "line_start": 40,
            "line_end": 42
          },
          {
            "file": "SKILL.md",
            "line_start": 42,
            "line_end": 44
          },
          {
            "file": "SKILL.md",
            "line_start": 44,
            "line_end": 44
          }
        ]
      },
      {
        "factor": "network",
        "evidence": [
          {
            "file": "references/pull-request.template.md",
            "line_start": 95,
            "line_end": 95
          },
          {
            "file": "references/pull-request.template.md",
            "line_start": 116,
            "line_end": 116
          },
          {
            "file": "references/pull-request.template.md",
            "line_start": 134,
            "line_end": 134
          },
          {
            "file": "references/pull-request.template.md",
            "line_start": 150,
            "line_end": 150
          }
        ]
      }
    ],
    "static_findings": [
      {
        "id": "external_commands:references/pull-request.template.md:89:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "references/pull-request.template.md",
        "line_start": 89,
        "line_end": 90,
        "snippet": "- **Before:** `oldMethod()`"
      },
      {
        "id": "external_commands:references/pull-request.template.md:90:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "references/pull-request.template.md",
        "line_start": 90,
        "line_end": 96,
        "snippet": "- **After:** `newMethod(options)`"
      },
      {
        "id": "network:references/pull-request.template.md:95:hardcoded-url",
        "category": "network",
        "severity": "low",
        "pattern": "Hardcoded URL",
        "file": "references/pull-request.template.md",
        "line_start": 95,
        "line_end": 95,
        "snippet": "🤖 Generated with [Claude Code](https://claude.com/claude-code)"
      },
      {
        "id": "network:references/pull-request.template.md:116:hardcoded-url",
        "category": "network",
        "severity": "low",
        "pattern": "Hardcoded URL",
        "file": "references/pull-request.template.md",
        "line_start": 116,
        "line_end": 116,
        "snippet": "🤖 Generated with [Claude Code](https://claude.com/claude-code)"
      },
      {
        "id": "network:references/pull-request.template.md:134:hardcoded-url",
        "category": "network",
        "severity": "low",
        "pattern": "Hardcoded URL",
        "file": "references/pull-request.template.md",
        "line_start": 134,
        "line_end": 134,
        "snippet": "🤖 Generated with [Claude Code](https://claude.com/claude-code)"
      },
      {
        "id": "network:references/pull-request.template.md:150:hardcoded-url",
        "category": "network",
        "severity": "low",
        "pattern": "Hardcoded URL",
        "file": "references/pull-request.template.md",
        "line_start": 150,
        "line_end": 150,
        "snippet": "🤖 Generated with [Claude Code](https://claude.com/claude-code)"
      },
      {
        "id": "blocker:references/pull-request.template.md:58:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "references/pull-request.template.md",
        "line_start": 58,
        "line_end": 59,
        "snippet": "- [ ] Integration tests pass"
      },
      {
        "id": "blocker:references/pull-request.template.md:147:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "references/pull-request.template.md",
        "line_start": 147,
        "line_end": 148,
        "snippet": "- [ ] All existing tests pass"
      },
      {
        "id": "external_commands:SKILL.md:36:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 36,
        "line_end": 36,
        "snippet": "- `references/PULL_REQUEST.template.md` - PR body templates for features, bugs, refactors"
      },
      {
        "id": "external_commands:SKILL.md:40:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 40,
        "line_end": 42,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:42:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 42,
        "line_end": 44,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:44:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 44,
        "line_end": 44,
        "snippet": "Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`"
      },
      {
        "id": "blocker:SKILL.md:30:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "SKILL.md",
        "line_start": 30,
        "line_end": 31,
        "snippet": "- Improving code review process"
      }
    ],
    "finding_verdicts": [
      {
        "id": "external_commands:references/pull-request.template.md:89:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.96,
        "reason": "Line 89 is a Markdown pull request template showing a before example, not executable Ruby or shell code. It contains no instruction to run commands or process user input."
      },
      {
        "id": "external_commands:references/pull-request.template.md:90:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.96,
        "reason": "Line 90 is a Markdown after example inside a breaking change section. It documents a method signature and does not execute a shell command."
      },
      {
        "id": "network:references/pull-request.template.md:95:hardcoded-url",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The URL is a static attribution link to Claude Code inside a PR template. It does not initiate a network request or send any repository data."
      },
      {
        "id": "network:references/pull-request.template.md:116:hardcoded-url",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The URL is repeated as static Markdown attribution in a quick PR template. There is no executable fetch, webhook, or exfiltration behavior."
      },
      {
        "id": "network:references/pull-request.template.md:134:hardcoded-url",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The hardcoded URL is only a Markdown link in a bug fix PR template. It does not cause network access by the skill."
      },
      {
        "id": "network:references/pull-request.template.md:150:hardcoded-url",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "The URL appears in static attribution text for a refactor PR template. It is not code and does not perform outbound communication."
      },
      {
        "id": "blocker:references/pull-request.template.md:58:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.93,
        "reason": "Line 58 is a checklist item saying integration tests pass. It does not describe network scanning, host discovery, or reconnaissance activity."
      },
      {
        "id": "blocker:references/pull-request.template.md:147:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.93,
        "reason": "Line 147 is a checklist item saying all existing tests pass. It is normal PR documentation and has no network reconnaissance intent."
      },
      {
        "id": "external_commands:SKILL.md:36:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 36 references a Markdown template file using inline code formatting. It is documentation metadata and not executable command syntax."
      },
      {
        "id": "external_commands:SKILL.md:40:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 40 opens a fenced code block for branch naming syntax. The block is illustrative documentation and contains no shell execution."
      },
      {
        "id": "external_commands:SKILL.md:42:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 42 closes the branch naming code block. It is Markdown formatting, not backtick-based command execution."
      },
      {
        "id": "external_commands:SKILL.md:44:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 44 lists conventional branch type labels using inline code formatting. These are literal labels, not commands."
      },
      {
        "id": "blocker:SKILL.md:30:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 30 says the skill can improve code review processes. This is a normal workflow capability and not network reconnaissance."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 2,
    "total_lines": 235,
    "audit_model": "codex",
    "audited_at": "2026-07-05T12:24:51.805Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Manage Git Pull Requests and Branch Workflows",
    "value_statement": "Teams need consistent branch names, PR descriptions, and review checklists. This skill guides Claude, Codex, and Claude Code through practical Git workflow decisions.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "Git workflow",
      "pull request template",
      "branch naming",
      "code review",
      "merge strategy",
      "developer workflow",
      "PR checklist"
    ],
    "actual_capabilities": [
      "Creates structured pull request descriptions with summaries, test plans, and checklists.",
      "Recommends branch naming conventions using type, issue number, and short description fields.",
      "Explains when to use squash, merge, or rebase strategies.",
      "Helps document breaking changes with migration notes.",
      "Provides quick templates for feature, bug fix, and refactor pull requests."
    ],
    "limitations": [
      "It does not run Git commands or inspect repository state by itself.",
      "It cannot verify that tests passed unless the user provides results.",
      "It does not enforce repository branch protection settings.",
      "It depends on team conventions supplied by the user."
    ],
    "use_cases": [
      {
        "title": "Prepare a Pull Request",
        "description": "Create a clear PR body with summary, motivation, changes, tests, screenshots, and breaking change notes.",
        "target_user": "Application developer"
      },
      {
        "title": "Standardize Team Branches",
        "description": "Define branch naming rules that match issue tracking and conventional change types.",
        "target_user": "Engineering lead"
      },
      {
        "title": "Improve Review Quality",
        "description": "Add practical checklists that help reviewers confirm tests, documentation, warnings, and issue links.",
        "target_user": "Code reviewer"
      }
    ],
    "prompt_templates": [
      {
        "title": "Draft a Basic PR",
        "prompt": "Create a pull request description for this change. Include a summary, motivation, changes, test plan, checklist, and breaking changes section.",
        "scenario": "Beginner user preparing a first complete pull request."
      },
      {
        "title": "Name a Branch",
        "prompt": "Suggest a branch name for this work using type, issue number, and a short description. Explain why the type fits.",
        "scenario": "Developer starting work from an issue or ticket."
      },
      {
        "title": "Review PR Quality",
        "prompt": "Review this pull request description for clarity, missing test details, breaking change notes, screenshots, and issue links.",
        "scenario": "Reviewer checking whether a PR is ready for team review."
      },
      {
        "title": "Plan a Merge Strategy",
        "prompt": "Recommend a merge strategy for this branch. Consider commit history, audit needs, review size, and whether a linear history matters.",
        "scenario": "Advanced user choosing between squash, merge, and rebase."
      }
    ],
    "output_examples": [
      {
        "input": "A developer added OAuth login and needs a pull request description.",
        "output": "A complete PR draft with a feature summary, user motivation, added authentication details, test checklist, screenshot prompt, and breaking change section."
      },
      {
        "input": "A team wants branch names linked to ticket numbers.",
        "output": "A branch naming recommendation such as feature, fix, refactor, docs, test, or chore, with guidance for issue number and short description use."
      },
      {
        "input": "A maintainer is unsure whether to squash or merge a feature branch.",
        "output": "A merge strategy recommendation based on history clarity, audit trail needs, branch size, and team review expectations."
      }
    ],
    "best_practices": [
      "Provide the ticket number, change summary, and test results before asking for PR text.",
      "Use the same branch type labels across repositories and documentation.",
      "Document breaking changes with clear migration steps."
    ],
    "anti_patterns": [
      "Do not use vague PR summaries that only repeat the title.",
      "Do not claim tests passed without providing actual results.",
      "Do not choose a merge strategy without considering team history rules."
    ],
    "faq": [
      {
        "question": "Can this skill create pull request templates?",
        "answer": "Yes. It provides full PR body sections and quick templates for feature, bug fix, and refactor work."
      },
      {
        "question": "Does this skill run Git commands?",
        "answer": "No. It provides workflow guidance and templates, but it does not execute Git commands by itself."
      },
      {
        "question": "Which tools can use this skill?",
        "answer": "The report lists support for Claude, Codex, and Claude Code."
      },
      {
        "question": "Can it help with branch naming?",
        "answer": "Yes. It recommends names using a change type, issue number, and short description."
      },
      {
        "question": "Can it choose a merge strategy?",
        "answer": "Yes. It explains squash, merge, and rebase options based on team needs."
      },
      {
        "question": "Is it suitable for code review process changes?",
        "answer": "Yes. It helps define checklists for tests, documentation, warnings, screenshots, and linked issues."
      }
    ]
  },
  "file_structure": [
    {
      "name": "references",
      "type": "dir",
      "path": "references",
      "children": [
        {
          "name": "pull-request.template.md",
          "type": "file",
          "path": "references/pull-request.template.md",
          "lines": 173
        }
      ]
    },
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 62
    }
  ]
}
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall