db-reset
Skill1 starsChanged 14 days agoApache-2.0View on GitHub
Fully reset the dev databases of Ringwerk and Spiegel (ALL their dev data is lost) — drop + recreate both and re-apply the schema; the treffsicher dev DB stays. Use only when explicitly asked to reset the dev DB.
- Deletes or force-pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- allanninal/claude-code-skillstheir own version, first seen Oct 17, 2026
- behradkhodayar/claude-code-py-ts-pgtheir own version, first seen Jul 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- allanninal/claude-code-skills★ 1same name
- behradkhodayar/claude-code-py-ts-pg★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- checkSkill
- commit-msgSkill
- consolidate-lessonsSkill
- coordinateSkill
- debugSkill
- implementSkill
- ingestSkill
- migrateSkill
- planSkill
- reviewSkill
- sync-graphSkill
- testSkill
- validateSkill
The file
Files
Resets the dev DBs ringwerk and spiegel in the shared dev Postgres. ALL their dev data is lost:
docker compose -f docker-compose.dev.yml up -d
until docker compose -f docker-compose.dev.yml exec -T db pg_isready -U postgres >/dev/null 2>&1; do sleep 1; done
for app in ringwerk spiegel; do
docker compose -f docker-compose.dev.yml exec -T db psql -v ON_ERROR_STOP=1 -U postgres -d postgres \
-c "DROP DATABASE IF EXISTS $app WITH (FORCE);" -c "CREATE DATABASE $app OWNER $app;" \
-c "REVOKE ALL ON DATABASE $app FROM PUBLIC;"
done
pnpm --filter ringwerk exec prisma db push # schema → ringwerk dev DB
pnpm --filter spiegel exec prisma db push # schema → spiegel dev DBThe dev DB treffsicher is not reset: Treffsicher has no code any more (ADR-033, stage 5), and the DB is a prod
copy that the account transfer reads in dev until the deletion date (1 February 2027). Never drop the volume
(down -v) for a reset, that would lose it too.
The same schema push runs in ./scripts/vereinsheim dev-setup (scripts/bootstrap-dev.sh).
First app request re-initialises admin + default disciplines (startup init; Spiegel creates its
admin at server start). For prod data instead of an empty DB, restore a backup with
pg_restore from backups/*.dump.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

