Guidelines for consistent commit hygiene, CI operations, and security in pull requests.

Install

mkdir -p .claude/skills/pr-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2965" && unzip -o skill.zip -d .claude/skills/pr-workflow && rm skill.zip

Installs to .claude/skills/pr-workflow

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

General guidelines for Commits, formatting, CI, dependencies, security
70 charsno explicit “when” trigger
Beginner

Key capabilities

  • Maintain atomic commit history
  • Enforce PR focus and size limits
  • Manage third-party dependency licenses
  • Exclude sensitive files from commits

How it works

The workflow mandates atomic commits and specific documentation for dependencies to ensure repository health and security.

Inputs & outputs

You give it
Code changes
You get back
Compliant PR and commit history

When to use pr-workflow

  • Review PR guidelines before submission
  • Ensure atomic commit history
  • Check for dependency license compliance
  • Verify sensitive files are excluded from commits

About this skill

PR Workflow Guide

Commit Practices

  • Atomic commits. Small, focused, single purpose
  • Don't mix: logic + formatting, logic + refactoring
  • Good message = easy to write short description of intent

Learn git rebase -i for clean history.

PR Guidelines

  • Keep PRs focused and small
  • Run relevant tests before submitting
  • Each commit tells part of the story

CI Environment Notes

If running as GitHub Action:

  • Max-turns limit in .github/workflows/claude.yml
  • OK to commit WIP state and push
  • OK to open WIP PR and continue in another action
  • Don't spiral into rabbit holes. Stay focused on key task

Security

Never commit:

  • .env files
  • Credentials
  • Secrets

Third-Party Dependencies

When adding:

  1. Add license file under licenses/
  2. Update NOTICE.md with dependency info

External APIs/Tools

  • Never guess API params or CLI args
  • Search official docs first
  • Ask for clarification if ambiguous

When not to use it

  • Mixing logic and formatting in one commit
  • Guessing API parameters

Prerequisites

GitCI environment access

Limitations

  • Requires manual adherence to commit standards
  • Limited to repository-level workflow guidelines

How it compares

It emphasizes strict separation of concerns and explicit dependency tracking over ad-hoc development practices.

Compared to similar skills

pr-workflow side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
pr-workflow (this skill)16moReviewBeginner
find-bugs57moNo flagsIntermediate
lint07moNo flagsBeginner
code-review03moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

find-bugs

davila7

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

529

lint

i3ringit

Use this agent when you need to run linting and code quality checks on Ruby and ERB files. Run before pushing to origin.

00

code-review

openzigs

Comprehensive code review workflow for pull requests. Validates against requirements (epic/issue), checks code quality, security (OWASP Top 10), performance, test coverage, and documentation. Leaves structured GitHub review with inline comments. Optionally hands off to Code Issue agent for fixes.

00

lisa-parity-code-review

CodySwannGT

Lisa-native code review of the current git diff. Walks every changed hunk and reports correctness bugs, security issues, and obvious defects as severity-ranked findings with file:line references. Vendor-neutral — the cross-agent equivalent of the upstream code-review command, runnable on Codex, agy,

00

auditing-pre-release-security

OneKeyHQ

Audits security and supply-chain risk between two git refs, 预发布安全审计

14

resolve-conflicts

antinomyhq

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.

81334

Search skills

Search the agent skills registry