Instruction file imported from cktnfla1234-svg/in-bite (.cursor/rules/deploy-after-changes.mdc). Copyright stays with the author.

Deploy after modifications

Name: deploy-after-changes
Author: cktnfla1234-svg

When you finish changes to this repo (application code, config, scripts, or SQL that ships with the app), deploy automatically unless the user explicitly asked not to push or not to deploy.

Run npm run build if you have not already confirmed a successful build in this turn.
Run npm run deploy -- "<type>: concise description>" from the project root, using a short English conventional-style subject (for example fix:, feat:, chore:). The script runs build again, commits any uncommitted changes with that message, and git push to trigger Vercel (GitHub main).

If git push fails (auth, conflicts), report the error and tell the user what is blocking; do not claim deploy succeeded.

Skip deploy only when: the user said not to deploy/push; there were no file edits and nothing to ship; or the task was documentation-only and the user did not ask for deploy.

{ "ocm": "1", "id": "cktnfla1234-svg-in-bite-deploy-after-changes-rule", "kind": "skill", "name": "deploy-after-changes", "description": "After code changes, run deploy (build, commit, push) so Vercel ships.", "publisher": "cktnfla1234-svg", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "After code changes, run deploy (build, commit, push) so Vercel ships." ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/cktnfla1234-svg/in-bite", "path": ".cursor/rules/deploy-after-changes.mdc", "ref": "72024d45d2afa144e951bbe0d9824ef8e90eda97", "url": "https://github.com/cktnfla1234-svg/in-bite/blob/72024d45d2afa144e951bbe0d9824ef8e90eda97/.cursor/rules/deploy-after-changes.mdc", "key": "cktnfla1234-svg/in-bite/.cursor/rules/deploy-after-changes.mdc" } }, "instructions": "# Deploy after modifications\n\nWhen you **finish** changes to this repo (application code, config, scripts, or SQL that ships with the app), **deploy automatically** unless the user explicitly asked not to push or not to deploy.\n\n1. Run `npm run build` if you have not already confirmed a successful build in this turn.\n2. Run **`npm run deploy -- \"<type>: concise description>\"`** from the project root, using a short English conventional-style subject (for example `fix:`, `feat:`, `chore:`). The script runs build again, commits any uncommitted changes with that message, and `git push` to trigger ", "cost": { "context_tokens": 233 } }

deploy-after-changes

About

Deploy after modifications

Use it

Manifest

Reviews