skills.rest
unfoldingWord
unfoldingWordOFFICIAL
Explore all skills by this author →
WebsiteGitHub

repo-verify

Compare local staging to remote Door43 master to verify repo-insert merges.

1|Updated Mar 25, 2026
Search Tags:#git#merge#branch#verify#repo#master#door43
One-click install
npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill repo-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-verify
Source: https://github.com/unfoldingWord/bp-assistant-skills/tree/main/.claude/skills/repo-verify
Command: npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill repo-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that a repo-insert workflow actually lands on the Door43 master branch by comparing local staging to remote content, preventing undetected merge failures.

Core Features & Use Cases

  • Validate that the staging branch is removed after a successful merge to master.
  • Confirm that master contains the intended content for the target Repo (e.g., en_tn, en_ult, en_ust).
  • Generate a concise report indicating merge success or failure and point out any discrepancy between local and remote repos.

Quick Start

Run repo-verify after a repo-insert to confirm the staging branch was merged and the changes exist on master.

Frequently Asked Questions about repo-verify

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

FAQPage Schema
How do I verify a git merge landed on the master branch?▼

To verify a git merge landed on master, compare your local staging branch to the remote master branch to confirm the intended content exists and detect any merge discrepancies.

How do I check if a staging branch was removed after a Door43 merge?▼

You can check if a staging branch was removed after a Door43 merge by comparing local staging to the remote master, which validates the merge and confirms the staging branch deletion.

What is the best way to detect discrepancies between local staging and remote master?▼

The best way to detect discrepancies between local staging and remote master is to run a verification process that compares the two, generating a concise report of any merge failures or content mismatches.

Can I confirm content changes exist on master for specific repositories like en_tn or en_ult?▼

Yes, you can confirm content changes exist on master for repositories like en_tn, en_ult, and en_ust by validating that the staging branch merged successfully and the expected content is present.

Why does my Door43 repo-insert fail to show changes on the remote master?▼

A Door43 repo-insert fails to show changes on remote master when the merge is unsuccessful, requiring a verification check to identify discrepancies between local staging and the remote master branch.

Do I need to run a verification check after every repo-insert workflow?▼

Yes, you need to run a verification check after every repo-insert workflow to validate successful merges, ensure the staging branch is removed, and confirm the master contains the expected content.

Related Skills

Explore More Software Engineering Skills→
unfoldingWordunfoldingWord
1

repo-insert

Insert AI-generated ULT, UST, or TN content into Door43 repo clones and merge via pull requests.

Official
Advanced
hwj123hwjhwj123hwj
4

resolving-merge-conflicts

Guide users through resolving git merge and rebase conflicts.

Community
Advanced
smp4smp4

pr-cleanup

Verify merged GitHub PRs and delete stale local and remote branches.

Community
Advanced
epologeeepologee
3

rebase-latest-default

Rebase the current Git branch onto the latest default branch.

Community
Advanced