skills.rest
Dektora
DektoraOFFICIAL
Explore all skills by this author →
GitHub

pr-branch

Create clean pull request branches by filtering spec-only commits.

Updated Jun 2, 2026
Search Tags:#git#code review#code maintenance#commit filtering#PR branch
One-click install
npx skills add https://github.com/Dektora/dekspec-public --skill pr-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-branch
Source: https://github.com/Dektora/dekspec-public/tree/main/plugins/dekspec/skills/pr-branch
Command: npx skills add https://github.com/Dektora/dekspec-public --skill pr-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps streamline code reviews by creating clean PR branches, ensuring that code reviewers see only the code-related changes without any干扰 from specification artifact churn.

Core Features & Use Cases

  • Clean PR Branches: Filters out spec-only commits from PR branches.
  • Mixed Code+Spec Commits: Cherry-picks mixed commits and strips spec-only files.
  • Code Review Optimization: Improves code review efficiency by removing spec noise.

Quick Start

Run the pr-branch skill on your main branch to generate a clean PR branch.

Frequently Asked Questions about pr-branch

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

FAQPage Schema
How do I create a clean pull request branch that excludes specification commits?▼

To create a clean pull request branch, selectively include only code-related commits by filtering out spec artifacts. This ensures reviewers see only relevant code changes without noise from specification churn.

How does cherry-pick filtering work for mixed code and spec commits?▼

Cherry-pick filtering for mixed commits works by selectively applying code changes while stripping spec-only files. This Git-based approach restores code-specific modifications to construct a separate, review-optimized branch.

How do I separate code changes from spec artifacts in Git for better code reviews?▼

Separate code changes from spec artifacts by constructing a dedicated PR branch that uses cherry-pick commands to filter commits. This process actively removes specification noise to optimize code review efficiency.

Can I use pr-branch to clean up a Git branch with active code development and specification work?▼

Yes, you can use this approach for projects with active code development and specification work. It operates within a Git environment to selectively include code-related commits while removing spec artifact noise from the target branch.

What is the best way to improve code review efficiency when specification churn is high?▼

The best way to improve code review efficiency is generating a clean PR branch that removes spec-only commits. By filtering out specification artifact noise, reviewers focus exclusively on relevant code-related changes.

What happens to mixed code and specification commits during PR branch construction?▼

During PR branch construction, mixed code and specification commits are cherry-picked and spec-only files are stripped away. This ensures the resulting branch contains only the code-related changes needed for review.

Related Skills

Explore More Software Engineering Skills→
Cogni-DAOCogni-DAO

Git Branch Feature Coordinator

Coordinate multi-PR feature branches via squash-merge into an integration branch.

Official
Advanced
MINT-IAMINT-IA

gsd-pr-branch

Filter planning commits from a Git branch to produce a clean PR branch.

Official
Intermediate
coco-researchcoco-research
264

gsd-pr-branch

Create a clean pull request branch by filtering out planning commits.

Community
Intermediate
ChatAndBuildChatAndBuild
1

commit-helper

Generate Conventional Commits commit messages and split commits via interactive rebasing.

Official
Intermediate