Menú
Stages all current changes and commits them to git with a useful message derived from the diff. Run with /commit.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Investigate a Starfield form or record type to understand its structure
Reviews recent git work across 3–7 days and proposes exactly 5 targeted improvements to code elegance, coherence, and style alignment. Run with /elegance at the start or end of a session to keep the codebase healthy.
Picks a random file from Retrograde.Library and runs a focused elegance review against it and its related files, proposing exactly 5 targeted improvements. Run with /spotlight for a quick quality check on undervisited code.
End-of-session workflow improvement. Reviews what was learnt and makes small, targeted updates to scripts, formlib, designlib, CLAUDE.md, and memory. Run with /kaizen at the end of a working session.
Discover what decoration items Starfield places around a given PackIn or Static in existing worldspaces, then generate C# array entries ready to paste into a BuildingDecoratorPass. Use when the user asks to find decorations for a science counter, workbench, or any other Starfield furniture PackIn.
Refactor a Retrograde procedural generation pass using established patterns and checklist
| name | commit |
| description | Stages all current changes and commits them to git with a useful message derived from the diff. Run with /commit. |
| user_invocable | true |
Commits everything that is currently modified or untracked. Derives a meaningful commit message from the actual diff rather than asking the user.
Run these in parallel:
git -C c:/Git/FrankyCLI status --short
git -C c:/Git/FrankyCLI diff HEAD
git -C c:/Git/FrankyCLI log --oneline -5
Read the output carefully:
Do NOT stage:
.env files or anything containing secretsbin/, obj/) — these should already be gitignoredIf any suspicious files appear in the status output, flag them and ask the user before proceeding.
Write a single-line subject (≤72 chars) that:
git log output)Examples of good messages for this project:
Add IndustryGroundFlattenPass topology passFix nullable FormLink guard in SpaceShipNoun cloneRefactor AITools to separate stateless and history-writing callsMove MathUtil helpers to shared Retrograde.LibraryIf the changes span multiple unrelated concerns, group them into a short multi-line message with a blank line separating the subject from a bulleted body — but prefer a clean single line when possible.
git -C c:/Git/FrankyCLI add -A
git -C c:/Git/FrankyCLI commit -m "<subject line>"
If a pre-commit hook fails:
--no-verify)git -C c:/Git/FrankyCLI push
If the push fails because the branch has no upstream, set it:
git -C c:/Git/FrankyCLI push -u origin HEAD
After a successful push, show the user:
git log -1 --oneline)