reset-local-submissions

Deletes local verification attempts so verification flows can be retested.

801|25|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/learntocloud/learn-to-cloud-app --skill reset-local-submissions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reset-local-submissions
Source: https://github.com/learntocloud/learn-to-cloud-app/tree/main/.github/skills/reset-local-submissions
Command: npx skills add https://github.com/learntocloud/learn-to-cloud-app --skill reset-local-submissions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

During local development of the Learn to Cloud app, verification attempts accumulate in the database and block re-testing of submission flows. This Skill resets those records safely through a guarded script instead of ad-hoc SQL.

Core Features & Use Cases

  • Guarded Reset Script: Runs scripts/reset_local_submissions.py from api/, which previews matches and asks for confirmation before deleting verification_attempts rows.
  • Scoped Filtering: Supports repeatable --user-id and --requirement-slug filters to reset only specific users or curriculum requirements.
  • Dry-Run and Non-Interactive Modes: --dry-run previews matches without deleting, and --yes skips confirmation for agent-driven workflows.
  • Use Case: After fixing a verification function, reset your local submissions for a specific requirement slug, then resubmit to confirm the fix end to end.

Quick Start

Ask the assistant to dry-run a reset of local verification submissions for a specific requirement slug, review the matched users and outcomes, then confirm the reset.

Frequently Asked Questions about reset-local-submissions

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

FAQPage Schema
How do I reset local verification submissions for retesting?

Run `uv run python scripts/reset_local_submissions.py` from the `api/` directory. The script previews matching verification attempts and asks for confirmation before deleting them. Use `--dry-run` first to review what will be removed.

How to reset verification attempts for a specific user or requirement?

Pass the repeatable filters `--user-id <github-user-id>` and `--requirement-slug <slug>` to the reset script. Slugs are resolved through the curriculum artifact, and only matching `verification_attempts` rows are deleted.

Can the reset script run against a production database?

No. The script refuses to run against non-local databases as a built-in safety guard. Do not bypass that guard or substitute ad-hoc SQL to delete verification attempts.

How do I run the reset non-interactively from an agent?

Use `--dry-run` first to summarize matched users, requirements, and outcomes, then rerun with `--yes` to skip the confirmation prompt. Always confirm the dry-run results before applying the deletion.

What happens if I run the reset script without any filters?

Without filters, the script resets every requirement for every local user by deleting all matching `verification_attempts` rows. It still previews the matches and requires confirmation before deleting.