skills.rest
marin-community
marin-communityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pull-request

Standardize GitHub pull request authoring and review within the Marin framework.

1.2k|146|Updated Mar 22, 2024
Search Tags:#testing#code review#documentation#pull request#developer workflow#github
One-click install
npx skills add https://github.com/marin-community/marin --skill pull-request-marin-community
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/marin-community/marin/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/marin-community/marin --skill pull-request-marin-community

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a standardized process for creating, describing, and reviewing pull requests, ensuring clarity, consistency, and adherence to project guidelines.

Core Features & Use Cases

  • PR Description Standards: Enforces concise and informative PR titles and bodies, including linking issues.
  • Pre-PR Checks: Guides users through essential local checks (linting, testing, link validation) before pushing code.
  • Review Process Guidance: Outlines both human (specification-first) and agent (compliance validation) review stages.
  • Use Case: When you need to create a new pull request for a bug fix, this Skill will help you write a clear description, ensure you've run all necessary tests, and understand how to link it to the relevant issue.

Quick Start

Use the pull-request skill to author a new pull request description for a bug fix.

Frequently Asked Questions about pull-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a standardized GitHub pull request description for a bug fix?▼

A standardized GitHub pull request description requires a concise, informative title and body that links to the relevant issue. Following PR description standards ensures clarity and consistency when authoring bug fixes.

How does the code review process work for agent reviewers?▼

The code review process for agent reviewers focuses on compliance validation against project guidelines. Human reviewers follow a specification-first stage, while agents validate formatting rules and predefined check execution.

Do I need to link issues in my pull request title and body?▼

Yes, linking issues in your pull request title and body is required. PR description standards enforce specific formatting rules that mandate concise titles and informative bodies with explicit issue linking.

What is the best way to validate documentation links before creating a pull request?▼

The best way to validate documentation links is by executing predefined local validation scripts before pushing code. Running these link checks as part of your pre-PR workflow ensures documentation accuracy.

Related Skills

Explore More Software Engineering Skills→
spinlockdevelopmentspinlockdevelopment
1

end-session

Consolidate repository state, docs, and memory before ending a development session.

Official
Advanced
SantiagoisperSantiagoisper

land-and-deploy

Merge pull requests, deploy code changes, and verify production readiness.

Community
Advanced
guille-galloguille-gallo

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged for Git repositories.

Community
Intermediate
KubeHealKubeHeal

github-issue-resolver

Diagnose and fix GitHub Actions failures, PR conflicts, and Dependabot PRs via GitHub CLI.

Official
Advanced