pr-commit-workflowThis skill should be used when creating commits or pull requests, enforcing a human-written PR structure, intent capture, and evidence in agentic workflows.
Install via ClawdBot CLI:
clawdbot install joshp123/pr-commit-workflowEnforce a high-signal commit workflow and a human-written PR format. Keep global process rules as source of truth and make PRs reviewable by humans and agents.
references/workflow-commit.md.references/workflow-pr.md.AGENTS.md or docs/agents/PROCESS.md, read it for repo-specific rules./tmp for PR body drafts and gh pr edit --body-file for updates.references/workflow-commit.md.references/commit-format.md.references/workflow-pr.md.references/pr-human-template.md verbatim.scripts/build_pr_body.sh to gather environment metadata if available.references/workflow-commit.md: commit checklist and evidence expectations.references/workflow-pr.md: PR creation/update flow, comment checks, and evidence rules.references/pr-human-template.md: human-written PR structure (must be used as-is).references/commit-format.md: commit message format and examples.scripts/build_pr_body.sh: environment metadata collector for PR prompt history section.Generated Mar 1, 2026
Maintainers use this skill to enforce consistent commit messages and PR templates across community contributions, ensuring human-written intent is captured for each change. It helps automate checks for evidence and process adherence, making reviews efficient for both humans and bots in collaborative projects.
Teams integrate this skill into CI/CD workflows to standardize pull request creation and updates, enforcing global rules from internal documentation like AGENTS.md. It ensures all code changes include human-supplied intent and metadata, reducing errors and improving audit trails in regulated environments.
Development agencies apply this skill to manage client projects by automating PR and commit workflows, using templates to capture project-specific requirements and evidence. It streamlines collaboration among distributed teams, ensuring consistent communication and compliance with client guidelines.
Academic or research teams use this skill to handle code and data versioning in repositories, enforcing structured commits and PRs with human-written descriptions for reproducibility. It aids in documenting intent and evidence for experiments, facilitating peer review and data integrity.
Offer this skill as part of a subscription-based platform that enhances Git workflows with AI-driven enforcement of PR and commit standards. It generates revenue through tiered pricing based on team size and advanced features like custom rule integration.
Provide expert services to integrate this skill into existing development environments, tailoring it to specific industry needs such as compliance or scalability. Revenue comes from project-based fees and ongoing support contracts for maintenance and updates.
Distribute the skill as open-source software to build community adoption, while monetizing through premium support, training, and customization services for enterprises. This model leverages widespread use to drive demand for specialized assistance.
š¬ Integration Tip
Ensure the skill reads repo-specific rules from AGENTS.md or docs/agents/PROCESS.md first, and use the provided scripts like build_pr_body.sh to automate metadata collection for consistent PR bodies.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.