jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/shipping-github-vercel-changes/SKILL.mdshipping-github-vercel-changes
Skill1 starsChanged 3 months agoMITView on GitHub
Use when completing repository work that should be committed, pushed, reviewed through a pull request, or promoted through development and production branches with Vercel deployment in mind.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- defining-brand-strategySkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- editing-for-clarity-and-toneSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- naming-brands-and-productsSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-launch-distributionSkill
- planning-safe-refactorsSkill
- planning-written-communicationSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- translating-figma-to-nextjsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 13
Never mix unrelated dirty work into the task.
- Distinctive: line 14
Create a descriptive branch for feature/fix work when currently on the default branch.
- Distinctive: line 15
Commit narrowly with messages that describe the delivered behavior.
- Distinctive: line 16
Run relevant gates before claiming readiness: diff check, lint, typecheck, tests, production build.
- Distinctive: line 20
Do not merge unless the user or repository workflow authorizes it.
- Distinctive: line 21
After merge, verify deployment status and runtime configuration when the task includes release delivery.
- Distinctive: line 25
Ensure required environment variables exist in the correct environments.
- Distinctive: line 26
Never paste secrets into source or PR body.
- Distinctive: line 27
Treat successful deployment as necessary but not sufficient.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shipping GitHub and Vercel Changes
Default branch model
Respect the repository's actual policy. When it uses dev and main, feature/fix branches target dev; release promotion goes from dev to main.
Workflow
- Inspect current branch, remote,
git status, and existing PRs before writing. - Never mix unrelated dirty work into the task.
- Create a descriptive branch for feature/fix work when currently on the default branch.
- Commit narrowly with messages that describe the delivered behavior.
- Run relevant gates before claiming readiness: diff check, lint, typecheck, tests, production build.
- Inspect runtime/UI when the change is visual or interactive.
- Reuse an existing matching PR rather than opening duplicates.
- Include summary, verification performed, screenshots when useful, known limitations, and migration/env implications in the PR.
- Do not merge unless the user or repository workflow authorizes it.
- After merge, verify deployment status and runtime configuration when the task includes release delivery.
Vercel specifics
- Distinguish Preview from Production configuration.
- Ensure required environment variables exist in the correct environments.
- Never paste secrets into source or PR body.
- Treat successful deployment as necessary but not sufficient; verify the deployed route when release correctness matters.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.