メニュー
Reset the OpenRegister development environment (stop, remove volumes, restart, install apps)
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | clean-env |
| description | Reset the OpenRegister development environment (stop, remove volumes, restart, install apps) |
Run the clean-env.sh script to fully reset the OpenRegister development environment.
This will:
Model check — only apply when this skill is run standalone. Skip this section entirely if this skill was called from within another skill — the calling skill is responsible for model selection.
Check the active model from your system context (it appears as "You are powered by the model named…").
"⚠️ You're on Sonnet. This skill runs a shell script — purely mechanical, no reasoning required. Haiku is a better fit and conserves quota for heavier tasks. Switch with
/model haiku, or proceed with Sonnet." Options: Proceed with Sonnet / Switch to Haiku first (stop here if switching)
"You're on Opus. This skill runs a shell script — purely mechanical, no reasoning required. Opus is overkill here and will waste quota unnecessarily. Please switch to Haiku (
/model haiku) and re-run."
Run the clean-env script:
bash .claude/scripts/clean-env.sh
Important: This is a destructive operation — it removes all database data and volumes. Only run when a full reset is intended.
After the script completes, verify the environment:
If any app fails to enable, try running manually:
docker exec nextcloud php occ app-enable <appname>
💡 If you switched models to run this command, don't forget to switch back to your preferred model with
/model <name>(e.g./model defaultor/model sonnet).
Create a Pull Request from the current branch — runs local checks, picks target branch, and opens the PR on GitHub
Analyze a project's OpenSpec from 8 persona perspectives and suggest additional features
Detect admin settings Vue components registered in the vue-router. Admin settings are rendered by Nextcloud's settings framework via `AdminSettings.php`; adding their Vue components to the in-app router exposes them as publicly-accessible frontend routes, bypassing all server-side access checks. ADR-004 hard rule. Observed 2026-04-30 on doriath where `/settings → AdminRoot` was a route in `src/router/index.js` (commit c7c72e9).
Run `composer audit` to check composer.lock dependencies for known CVEs. Invoked by the builder before push and the reviewer's mandatory block. Mirrors the orchestrator's `composer-audit` quality gate.
Scan lib/ for forbidden debug helpers (var_dump / die / error_log / print_r / dd / dump) that should not ship. Invoked by the builder before push, by the reviewer as Mandatory Step 2, and by the fixer during a retry. Mirrors the orchestrator's `forbidden-patterns` quality gate.
Detect DOM data-attribute reads in `.vue`/`.js`/`.ts` files (e.g. `document.getElementById('x').dataset.version`) used to pull server-side data into the frontend. The Nextcloud-idiomatic pattern is `IInitialState::provideInitialState()` in PHP + `loadState()` from `@nextcloud/initial-state` in Vue. DOM data-attributes break on CSP-hardened instances and bypass the canonical pattern documented in ADR-004. Observed 2026-04-30 on doriath where `AdminRoot.vue` read `document.getElementById('doriath-settings').dataset.version`.