skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

truthful-draft-pr-scope

Document landed changes and deferred context in draft pull requests.

3|3|Updated Apr 13, 2026
Search Tags:#git#branch-management#pull-request#draft-pr#scope-verification#pr-scope
One-click install
npx skills add https://github.com/quaid-app/quaid --skill truthful-draft-pr-scope
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: truthful-draft-pr-scope
Source: https://github.com/quaid-app/quaid/tree/main/.squad/skills/truthful-draft-pr-scope
Command: npx skills add https://github.com/quaid-app/quaid --skill truthful-draft-pr-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams open a narrow, honest draft PR when the branch context is broader than the landed slice, preventing over-claiming.

Core Features & Use Cases

  • Verify that the PR only contains landed changes and documents any non-landed context separately.
  • Ensure the PR body describes the exact scope, including which changes are included and which are deferred.
  • Apply to feature branches, planning branches, or documentation branches where scope granularity matters.

Quick Start

Draft a draft PR that documents only the landed scope and notes any broader context that is not included.

Frequently Asked Questions about truthful-draft-pr-scope

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

FAQPage Schema
How do I open a draft PR when my branch has broader context than the landed changes?▼

Open a draft PR documenting only the landed changes and separately noting the non-landed context. This transparent scope communication prevents over-claiming when your feature branch ancestry exceeds the implemented slice.

What is draft PR scope verification for a feature branch?▼

Draft PR scope verification ensures the pull request body describes the exact landed scope while explicitly identifying deferred work. It keeps the PR in draft until the full scope of your branch is landed.

How do I document non-landed work in a planning branch pull request?▼

Document non-landed work by separating it from landed changes in the PR body. Clearly state which changes are included and which are deferred, maintaining the pull request as a draft until the full scope is complete.

Can I use a draft PR for a documentation branch with partial scope?▼

Yes, draft PRs work for documentation branches where scope granularity matters. They allow you to verify the PR only contains landed changes and transparently communicate the broader branch context that is not yet included.

Why does my draft PR over-claim changes from the branch ancestry?▼

Draft PRs over-claim when the branch context is broader than the landed slice. Clarify the landed scope by documenting only implemented changes and noting any non-landed context separately to ensure transparent scope communication.

What's the best way to keep a draft PR honest about unimplemented features?▼

Keep a draft PR honest by verifying it only contains landed changes and documenting any non-landed context separately. Apply this to feature branches or planning branches where only a subset of work is currently landed.

Related Skills

Explore More Software Engineering Skills→
Noisemaker111Noisemaker111

warm-feature-flow

Prepare a clean Git workspace and draft PR pipeline for new features.

Community
Intermediate
alexica00alexica00

pr

Analyze code changes and generate structured pull request descriptions.

Community
Advanced
erclxerclx
2

git-ship

Synchronize documentation, stage git changes, and create pull requests.

Community
Advanced
jwmossmozjwmossmoz
3

lando

Polls the Lango API to determine landing job statuses and outcomes.

Community
Basic