skills.rest
fcsonline
fcsonlineCOMMUNITY
Explore all skills by this author →
Website𝕏@openfcsonlineGitHub

pr-workflow

Enforces PR-based development workflowbforking direct pushes to the main branch.

49|15|Updated Apr 6, 2026
Search Tags:#git#workflow#branching#pr#code-review#ci#pull-request
One-click install
npx skills add https://github.com/fcsonline/droneroute --skill pr-workflow-fcsonline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/fcsonline/droneroute/tree/main/.opencode/skills/pr-workflow
Command: npx skills add https://github.com/fcsonline/droneroute --skill pr-workflow-fcsonline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR-based development workflow prevents direct pushes to main by routing all changes through reviews and approvals, reducing deployment risk and ensuring traceability.

Core Features & Use Cases

  • Enforces branch creation for new work (feat/ or fix/) and clear naming conventions
  • Requires pull requests with linked issues and changelog entries
  • Integrates with CI to validate changes before merging
  • Covers feature, bug fix, and refactor tasks to maintain quality and history

Quick Start

Follow the PR workflow: create a feature branch, open a PR with a changelog entry, and ensure CI checks pass before merging.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I enforce a pull request workflow to prevent direct pushes to main?▼

To enforce a pull request workflow, you must route all changes through reviews and approvals, prohibiting direct pushes to main. This reduces deployment risk by ensuring traceability for feature development, bug fixes, and refactors.

What is PR-driven development and when do I need it for my codebase?▼

PR-driven development is a process routing all codebase changes through pull requests. You need it to prevent direct pushes to main, ensuring mandatory branch creation, CI checks, changelog entries, and linked issues for quality and history.

How do I create a feature branch and open a PR with required changelog entries?▼

To create a PR, start by creating a feature branch with clear naming conventions like feat/ or fix/. Then open a pull request including a changelog entry and a linked issue, ensuring CI checks pass before merging.

Does this PR workflow guardian integrate with CI to validate changes before merging?▼

Yes, this PR workflow guardian integrates with CI to validate changes. It ensures pull requests include CI checks before merging, maintaining quality and history across feature, bug fix, and refactor tasks.

What are the limitations of using PR-based workflows for refactoring tasks?▼

PR-based workflows require mandatory branch creation and changelog entries for refactoring tasks. A limitation is that routing all changes through reviews and approvals may slow down rapid deployments compared to direct pushes.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

land-and-deploy

Merge pull requests, deploy changes, and verify production health via CI/CD pipelines.

Community
Advanced
Clawdi-AIClawdi-AI
4

prepare-pr

Rebase GitHub PRs onto main, apply review fixes, and run tests.

Official
Advanced
tomas-utomas-u
1

code-review

Analyze code diffs against stories, tests, and coding standards.

Community
Advanced
jota-batutajota-batuta

git-workflow-and-versioning

Standardize trunk-based development and atomic commits for CI/CD workflows.

Community
Intermediate