skills.rest
learntocloud
learntocloudOFFICIAL
Explore all skills by this author →
Website𝕏@learntocloudGitHub

reset-prod-submissions

Deletes a user's production verification attempts after preview and explicit confirmation.

801|25|Updated Jan 10, 2026
Search Tags:#data deletion#Database#postgreSQL#Production#Operations#user reset#verification attempts
One-click install
npx skills add https://github.com/learntocloud/learn-to-cloud-app --skill reset-prod-submissions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reset-prod-submissions
Source: https://github.com/learntocloud/learn-to-cloud-app/tree/main/.github/skills/reset-prod-submissions
Command: npx skills add https://github.com/learntocloud/learn-to-cloud-app --skill reset-prod-submissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a controlled, auditable procedure for removing a user's production verification attempts in the Learn to Cloud app, preventing accidental or overly broad deletions of progress data.

Core Features & Use Cases

  • Scoped Deletion: Resolves the GitHub username and requirement slug to exact IDs, then deletes only the previewed rows from verification_attempts in a single transaction.
  • Preview and Confirmation: Shows the exact count and scope of matching rows and requires explicit user confirmation before any deletion occurs.
  • Post-Delete Verification: Uses RETURNING id and re-queries after commit to report deleted and remaining counts.
  • Use Case: A learner asks support to reset their progress on one hands-on project after a bad submission; the operator previews the matching attempts, confirms the scope, and deletes only those rows.

Quick Start

Ask the assistant to reset prod submissions for a specific GitHub username, optionally scoped to one requirement, and confirm the previewed rows before deletion.

Frequently Asked Questions about reset-prod-submissions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reset a user's production verification attempts?▼

Resolve the GitHub username through the users table, preview matching rows in verification_attempts scoped by user_id, show the exact count, obtain explicit confirmation, then delete the previewed scope in one transaction and re-query to verify.

How do I reset progress for only one requirement?▼

Resolve the requirement slug to its UUID from the current curriculum artifact and include requirement_uuid in the delete predicates. The skill never broadens a requirement-scoped reset to all of the user's attempts.

Does resetting submissions require updating progress counters?▼

No counter updates are needed. Progress is derived directly from verification_attempts, so deleting the attempt rows automatically changes the user's derived progress.

Why does the reset stop without deleting anything?▼

The procedure stops if the schema, username, or requirement slug cannot be resolved unambiguously. This guard prevents deleting the wrong user's data or the wrong requirement's attempts.

Can I use the submissions or verification_jobs tables for resets?▼

No, those tables are retired. All reset operations must target only the verification_attempts table, which is the current source of truth for progress.

Related Skills

Explore More Software Engineering Skills→
3horizons3horizons

database-management

Monitor Azure PostgreSQL health, connections, backups, and database sizes.

Official
Intermediate
timequitytimequity
6

progress-manager

Track and display user course progress in a versioned JSON file.

Official
Basic
hajrasarwar11hajrasarwar11

database

Create and query Replit PostgreSQL databases with read-only production access.

Community
Advanced
Impertio-StudioImpertio-Studio
2

mariadb-impl-backup-restore

Automate MariaDB backup creation and restoration with mariabackup and mariadb-dump.

Official
Advanced