Ship a pull request end-to-end with worktree audit, pre-flight gates, review, and merge.
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill send-it-sassy-dog
Please help me install this Agent Skill. Skill: send-it Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/send-it Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill send-it-sassy-dog
Closes #N lines, derive the correct base branch, then hand watch-and-merge off to the pr-shepherd skill. - Use Case: You finish a feature branch with a schema change and some stray untracked files. Invoke the skill and it stashes the unrelated files, regenerates the migration, runs pre-flight checks, gets the diff reviewed, opens a properly templated PR, and merges it after checks pass. ## Quick Start Ask the agent to ship the current branch by saying "send it" or "open the PR for this branch" in a repo configured with .claude/sassy-dog/send-it.md.High-intent search queries and answers about installing and using this skill.
Invoke the skill with a phrase like "send it" or "ship this branch" in a configured repo. It audits the worktree, runs pre-flight checks, dispatches a review agent, creates a template-compliant PR, and delegates watching and merging to the pr-shepherd skill.
Pre-flight commands come from the `preflight_commands` field in `.claude/sassy-dog/send-it.md`, generated by the setup-config skill. The skill runs them exactly as written and never substitutes inferred commands, since a guessed command that exits 0 without testing anything is indistinguishable from a pass.
The worktree audit still runs because it is universal, but the skill stops before pushing and reports the missing config. It then offers to run the setup-config skill to generate the repo's configuration, and never writes config itself.
Yes, but only when a `stacked_prs:` block exists in the repo config. It derives the correct base branch instead of defaulting to the default branch, links the PRs via the GitHub stacks API, and hands off merging since lower layers must land first.
The review gate always reports an outcome so a missing review never looks like a passing one. SKIPPED means no review agent could be dispatched or the repo opted out; NO REPORT means the agent ran but returned no readable report.
No. The guardrails forbid pushing past a failing pre-flight check and merging past red CI. Watch and merge are delegated to the pr-shepherd skill, which enforces mergeable state before acting.
harleypigAudit global and local Claude configurations for settings, rules, skills, and plugins.
danielbere1973Monitors Remotion pull requests, resolves conflicts and CI failures, then merges them.
danalexilewisClean up worktrees, stale branches, and orphaned directories after work sessions.
JeqqeRun parallel ship pipelines on leased worktrees and integrate branches into one PR.