Menu
A skill to handle the last user input.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | last-user-input |
| description | A skill to handle the last user input. |
| user-invocable | true |
NEVER STOP YOUR IMPLEMENTATION PROCESS WITHOUT ASKING THE USER IF THEY HAVE ANY LAST REQUESTS OR CHANGES. ALWAYS CONFIRM WITH THE USER BEFORE FINALIZING YOUR IMPLEMENTATION TO ENSURE THAT YOU HAVE MET THEIR EXPECTATIONS AND REQUIREMENTS. WHEN USER ANSWERS "YES" TO THE LAST QUESTION, YOU MUST READ THE #file:../../tmp/xxx/user-inputs.md FILE AGAIN TO CHECK FOR ANY UPDATES OR CHANGES IN THE USER'S REQUIREMENTS OR EXPECTATIONS AND ADJUST YOUR IMPLEMENTATION PROCESS ACCORDINGLY, STARTING THE PROCESS OVER. THIS IS CRUCIAL TO ENSURE THAT YOUR IMPLEMENTATION IS ALIGNED WITH THE USER'S NEEDS AND THAT YOU HAVE NOT MISSED ANY IMPORTANT DETAILS. ON "YES" ANSWER, YOU MUST NOT STOP YOUR IMPLEMENTATION PROCESS IMMEDIATELY, YOU MUST START THE PROCESS OVER. THIS MEANS THAT YOU MUST RE-READ THE USER INPUTS, UPDATE YOUR TASKS AND SPECIFICATIONS IF NEEDED, AND THEN CONTINUE WITH THE IMPLEMENTATION PROCESS AS USUAL, ENSURING THAT YOU ADDRESS ANY NEW OR UPDATED REQUIREMENTS FROM THE USER. IT IS THEN POSSIBLE YOU ASK THE USER MANY TIMES IF THEY HAVE ANY LAST REQUESTS OR CHANGES, AND EACH TIME THEY ANSWER "YES", YOU MUST START THE IMPLEMENTATION PROCESS OVER, RE-READING THE USER INPUTS AND ADJUSTING YOUR IMPLEMENTATION ACCORDINGLY UNTIL THE USER ANSWERS "NO", AT WHICH POINT YOU CAN FINALIZE YOUR IMPLEMENTATION AND MARK THE TASK AS COMPLETE. THIS ITERATIVE PROCESS IS ESSENTIAL TO ENSURE THAT YOUR IMPLEMENTATION IS FULLY ALIGNED WITH THE USER'S EXPECTATIONS AND REQUIREMENTS. DO NOT STOP IF YOU HAVE OPEN QUESTIONS OR IF YOU ARE NOT SURE ABOUT SOMETHING, YOU MUST WRITE THE QUESTIONS IN THE #file:../../tmp/xxx/user-inputs.md UNDER A NEW "OPEN QUESTIONS" SECTION. ADD ASK USER FOR "last input". THE USER WILL REVIEW AND PROVIDE ANSWER IN THE SAME FILE. THIS WAY YOU CAN CONTINUE YOUR IMPLEMENTATION WITHOUT INTERRUPTION WHILE STILL ENSURING THAT YOU ADDRESS ANY UNCERTAINTIES OR OPEN QUESTIONS WITH THE USER IN A TIMELY MANNER. IF YOU ARE IN AUTO-APPROVE MODE, DO NOT ANSWER YOURSELF. THE USER MUST ANSWER HIMSELF.
YOU ARE ONLY ALLOWED TO STOP WHEN THE USER CONFIRMS ASK YOU TO STOP USING AN EXPLICIT CONFIRMATION.
Run pgTAP SQL tests using the repository wrapper. Use when asked to "run pgtap tests", "execute db tests", "run tests for migration test-NNN-*.sql", or "run pg_prove on tests directory". Works together with the create-migration skill to execute the exhaustive tests authored for a migration.
Manage Phinx DB migrations up and down. Use when asked to "run phinx migrate", "rollback last migration", "check migration status", "apply one migration", or "run phinx with --count=1", "migrate up", "migrate down". Works together with the create-migration skill for creating migration files and with the pgtap skill for running tests.
Create Phinx PHP database migrations with exhaustive pgTAP SQL test suites for the GeoKrety website database. Use when asked to "create a migration", "create a phinx migration", "create a phinx migration with tests", "add a database migration", "add a column", "create a table", "add a trigger", "create a database change", "write db migration tests", or any variant of database schema evolution tasks. Generates migration files following existing patterns, validates PHP syntax, creates comprehensive pgTAP tests targeting ~100% coverage and edge cases, then runs a DBA + critical-thinking review loop before applying. Works together with the phinx and pgtap skills.
Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices.
An expert in the GeoKrety system, including its database schema, analytics, and operational practices. This skill can answer questions about the system, help with database queries, and provide insights into the data and its structure.
Create optimized multi-stage Dockerfiles for any language or framework
