last-user-input

Étoiles0

Forks0

Mis à jour29 mars 2026 à 07:52

A skill to handle the last user input.

Installation

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.

Source

geokrety

geokrety/geokrety-stats

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	last-user-input
description	A skill to handle the last user input.
user-invocable	true

Last User Input Skill

if you are actually working on a task, you MUST read the #file:../../tmp/xxx/user-inputs.md file to get the latest user inputs and ensure that your implementation is aligned with the user's expectations and requirements. Else check for a #file:../../tmp/user-inputs.md file for the latest user inputs that you should be aware of.
if you have completed the implementation and are in the final stages of review, you MUST ask the user a "yes/no" question to confirm if they have any last requests or changes before you finalize the implementation and mark the task as complete. If the user answers "yes", 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. If the user answers "no", you MUST finalize the implementation and mark the task as complete.
you MUST sync the #tool:todo with the tasks defined in the #file:../../tmp/xxx/tasks.md file to ensure that you are always working on the most relevant and up-to-date tasks.
you MUST ensure that your implementation is consistent with the latest user inputs and that you have addressed all the points defined in the #file:../../tmp/xxx/user-inputs.md file before finalizing your implementation.

EXTREMELY IMPORTANT NOTES

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.

How to ask the user for last input?

you MUST use the #tool:vscode/askQuestions (or other ask user tool) to present the question interactively to the user. The question should be a simple "yes/no/free text" question asking if they have any last requests or changes before you finalize the implementation and mark the task as complete. For example: "Do you have any last requests or changes before I finalize the implementation? Please answer 'yes' or 'no' or provide your own input."

THE MOST IMPORTANT

YOU ARE ONLY ALLOWED TO STOP WHEN THE USER CONFIRMS ASK YOU TO STOP USING AN EXPLICIT CONFIRMATION.

Plus depuis ce dépôt

même dépôt

pgtap

geokrety/geokrety-stats

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.

2026-03-290

phinx

geokrety/geokrety-stats

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.

2026-03-210

create-migration

geokrety/geokrety-stats

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.

2026-03-160

prompt-builder

geokrety/geokrety-stats

Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices.

2026-03-110

geokrety-system-expert

geokrety/geokrety-stats

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.

2026-03-100

multi-stage-dockerfile

geokrety/geokrety-stats

Create optimized multi-stage Dockerfiles for any language or framework

2026-03-100

Last User Input Skill

if you are actually working on a task, you MUST read the #file:../../tmp/xxx/user-inputs.md file to get the latest user inputs and ensure that your implementation is aligned with the user's expectations and requirements. Else check for a #file:../../tmp/user-inputs.md file for the latest user inputs that you should be aware of.

if you have completed the implementation and are in the final stages of review, you MUST ask the user a "yes/no" question to confirm if they have any last requests or changes before you finalize the implementation and mark the task as complete. If the user answers "yes", 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. If the user answers "no", you MUST finalize the implementation and mark the task as complete.

you MUST sync the #tool:todo with the tasks defined in the #file:../../tmp/xxx/tasks.md file to ensure that you are always working on the most relevant and up-to-date tasks.

you MUST ensure that your implementation is consistent with the latest user inputs and that you have addressed all the points defined in the #file:../../tmp/xxx/user-inputs.md file before finalizing your implementation.

EXTREMELY IMPORTANT NOTES

How to ask the user for last input?

you MUST use the #tool:vscode/askQuestions (or other ask user tool) to present the question interactively to the user. The question should be a simple "yes/no/free text" question asking if they have any last requests or changes before you finalize the implementation and mark the task as complete. For example: "Do you have any last requests or changes before I finalize the implementation? Please answer 'yes' or 'no' or provide your own input."