redeploy-frontend

Triggers a Vercel redeploy by pushing a timestamp comment change via an isolated git worktree.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/timi-ty/agent-forge --skill redeploy-frontend-timi-ty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redeploy-frontend
Source: https://github.com/timi-ty/agent-forge/tree/main/skills/redeploy-frontend
Command: npx skills add https://github.com/timi-ty/agent-forge --skill redeploy-frontend-timi-ty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Forcing a Vercel redeploy normally requires either using the Vercel dashboard or pushing an empty commit, both of which interrupt your flow or risk touching your working directory. This Skill pushes a harmless timestamp comment change to the deploy branch using a separate git worktree, so your local uncommitted changes are never disturbed. ## Core Features & Use Cases - Worktree-based isolation: Creates a temporary git worktree at the remote branch state, so the redeploy works even with uncommitted local changes in your main working directory. - Auto-detection of project config: Detects the package manager (pnpm, yarn, bun, npm) from lock files, finds the deploy branch, and locates the timestamp file by searching for an existing // redeploy: marker. - Pre-push build validation: Runs the build locally in the worktree, auto-fixes prettier formatting failures, and aborts safely on non-trivial errors like TypeScript or ESLint failures. - Use Case: You fixed a bug and merged to main, but Vercel did not pick up the deploy. Ask the agent to trigger a redeploy, and it pushes a timestamp comment commit without touching your in-progress work. ## Quick Start Trigger a Vercel redeploy of the frontend on the current branch.

Frequently Asked Questions about redeploy-frontend

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

FAQPage Schema
How do I trigger a Vercel redeploy without pushing real code changes?

Push a trivial commit that updates a `// redeploy:` timestamp comment in a source file. Vercel detects the new commit on the deploy branch and starts a fresh deployment with no functional code change.

Can I redeploy the frontend with uncommitted local changes?

Yes. The workflow creates a separate git worktree at the remote branch state, so your main working directory and uncommitted changes are never touched. The timestamp commit is made and pushed entirely from the temporary worktree.

Does this work with pnpm, yarn, bun, and npm projects?

Yes. The package manager is auto-detected from lock files at the repo root, preferring pnpm-lock.yaml, then yarn.lock, bun.lockb, and package-lock.json. The detected manager is used for install, build, and format commands.

What happens if the local build fails before pushing the redeploy commit?

Prettier-only failures are auto-fixed with the format script and the build is retried. Non-trivial failures like ESLint or TypeScript errors abort the workflow, clean up the worktree, and report the full build output without pushing anything.

Why does the redeploy use a git worktree instead of the current branch?

Git forbids checking out the same branch in two worktrees, and the user's main worktree already has the deploy branch checked out. A detached-HEAD worktree at origin/branch allows merging unpushed local commits and pushing safely without conflicts.