Commits changes, runs checks, pushes branches, and creates GitHub pull requests.
npx skills add https://github.com/dyad-sh/dyad --skill dyad-pr-push
Please help me install this Agent Skill. Skill: dyad:pr-push Source: https://github.com/dyad-sh/dyad/tree/main/.claude/skills/pr-push Command: npx skills add https://github.com/dyad-sh/dyad --skill dyad-pr-push
Publishing local work to GitHub involves many repetitive steps—staging files, writing commit messages, running formatters and linters, pushing branches, and drafting PR descriptions. This Skill automates that entire publish flow so a branch ends up pushed with a reviewer-useful PR in one operation.
npm run fmt, npm run lint:fix, and npm run ts, then pushes to the correct remote.dyad-sh/dyad:main with a validated ## Summary section, or refreshes stale agent-authored text on existing PRs while preserving human-written notes.main/master directly, creates a feature branch when needed, handles fork remotes and bot accounts, and retries pushes with fallback remotes on permission errors.Ask the agent to publish the current work to GitHub using the pr-push skill, and it will commit, check, push, and open or update the pull request.
High-intent search queries and answers about installing and using this skill.
Run the pr_push.sh script with PR_PUSH_COMMIT_MESSAGE, PR_PUSH_PR_TITLE, and PR_PUSH_PR_BODY_FILE set. It stages changes, runs fmt, lint:fix, and typecheck, pushes to the appropriate remote, and creates the PR with gh pr create.
The script refuses to push main or master directly. It automatically creates a timestamped feature branch based on the changed files, commits the work there, and pushes that branch instead.
No, the script only runs npm run fmt, npm run lint:fix, and npm run ts. The agent decides separately whether to run npm test for broad changes or a targeted test command; GitHub CI runs the full suite.
The script retries without GitHub token environment variables, then falls back to the default remote or an upstream remote if one exists. It only fails after exhausting these fallback options.
No. When the active GitHub account is a bot, the script skips PR creation and instead outputs a PR creation link along with the suggested title and body for manual submission.
It treats package-lock.json modifications as spurious when package.json is unchanged, restoring the lockfile to avoid noise commits. Lockfile changes are kept only when package.json is also modified.
ai-pivotUpdate AGENTS.md and docs/agent/ files after code changes.
dojoengineCreate or update GitHub pull requests from the current branch to main and initiate CI checks.
JiggerFMap PR diff files to affected test suites and run targeted vitest commands.
Thanh-aperoAutomates Git operations with conventional commit splitting and secret security scans.