Menu
Internal skill — called by other skills after code is approved and tested. Commits and pushes changes to main. Handles missing git identity and GitHub auth in plain English for non-technical users.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when user requests a single standalone UI element — a button, form, card, input, or similar — with no broader feature context
Use when something is broken — error messages present, user says broken/not working/bug/fix/error
Use when the user wants to share their app with others or get a public URL — triggers include "deploy", "publish", "go live", "release", "share it", "I want a URL", "give me a link", "make it live", "show others", "put it online", "launch it"
Use when user describes anything to build — this is the default skill for all feature requests not matched by a higher-priority skill
Use when user needs to store, retrieve, or persist data with no UI involved — pure data layer work
User-invocable entry point for the Vipps frontend stack. Triggered explicitly by `/new-vipps-project`. Activates the React/Vite/TypeScript/Tailwind/IndexedDB/AKS plugin context, scaffolds the project, then routes all subsequent requests through this plugin.
| name | git |
| description | Internal skill — called by other skills after code is approved and tested. Commits and pushes changes to main. Handles missing git identity and GitHub auth in plain English for non-technical users. |
Commit and push approved changes to main. This skill is called internally — never triggered directly by the user.
Run: git config user.name and git config user.email
If either is empty, ask the user:
"Before I can save your changes, I need a name and email to label them with. What should I use? (These are just labels — they can be anything.)"
Then run:
git config --global user.name "NAME"
git config --global user.email "EMAIL"
Run: git ls-remote --heads origin (10-second timeout)
If it fails, tell the user:
"I can't reach GitHub right now. This usually means you're not logged in yet. Please run this in your terminal and tell me when it's done:
gh auth login"
Wait for confirmation, then retry once.
If it still fails:
"I wasn't able to connect to GitHub. Your changes are saved on your computer — you can push them later by saying 'push my changes'."
Stop here. Do not proceed to step 3.
git add -A
git commit -m "COMMIT_MESSAGE"
git push origin main
Generate COMMIT_MESSAGE from the feature description — short, plain English, no jargon (e.g. add search box, add login form).
If push fails with a conflict:
git pull --rebase origin main then git push origin main"I ran into a conflict saving your changes. This is rare — please ask a developer for help."
Tell the user:
"Done! Your changes are saved and GitHub is building the latest version."