pr-push_skill

This skill commits uncommitted changes, runs linting, fixes issues, and pushes the current feature branch to GitHub autonomously.
  • TypeScript

19.7k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dyad-sh/dyad --skill pr-push

  • SKILL.md8.7 KB

Overview

This skill automates committing any local changes, running lint and tests, applying fixes, and pushing the current feature branch to GitHub. It completes all steps autonomously without asking for confirmation and ensures a pull request is created or updated. It also records session learnings and reports the final PR URL and a concise summary of actions.

How this skill works

The skill inspects the current git branch, stages and commits uncommitted changes (excluding secrets and unwanted artifacts), runs formatter/linter and TypeScript checks, and fixes issues either automatically or by editing files. It runs the test suite, amends commits if lint made changes, determines the correct remote, pushes with --force-with-lease, and creates or updates a GitHub PR using the gh CLI. Finally, it removes a specific review label if present and records learnings in repo docs.

When to use it

  • You have local work that needs to be committed, linted, tested, and pushed without manual steps.
  • You want an automated, auditable PR creation or update from a feature branch.
  • You need consistent pre-push checks (fmt, lint:fix, TypeScript, tests) applied before pushing.
  • You want session learnings recorded automatically after a push.

Best practices

  • Never run this skill from main/master; it will create a descriptive feature branch if needed.
  • Keep secrets and build artifacts out of commits (.env, node_modules/, *.key, *.pem, .DS_Store, logs).
  • Avoid spurious package-lock.json commits unless package.json changed.
  • Ensure gh CLI is authenticated and remotes are configured (origin/upstream) for predictable pushes.
  • Prefer small, focused commits so lint fixes can be amended cleanly into the last commit.

Example use cases

  • Finish a local bugfix: commit changed files, auto-fix lint, run tests, and push with a PR created.
  • Polish a new feature branch after manual edits and ensure all checks pass before pushing.
  • Recover from local formatting fixes by amending the last commit and force-pushing safely.
  • Capture session notes and troubleshooting tips into AGENTS.md or rules/ after a successful push.

FAQ

No. If run on main/master it creates a descriptive feature branch and switches to it before committing or pushing.

What does it do with files that should never be committed?

It automatically excludes common secrets and artifacts (.env*, node_modules/, *.key, .DS_Store, logs). It reports any ignored files in the final summary.

How does the skill choose which remote to push to?

It prefers an existing upstream if set. If none, it checks for an existing PR headRepository to match a local remote, otherwise falls back to origin and, on permission errors, attempts upstream per repo workflow.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
pr-push skill by dyad-sh/dyad | VeilStrat