m/mtm-ddwipe
1
0
Fork 0
Code Issues Releases Activity

docs: tighten project conventions for mtm-ddwipe

Browse Source
This commit is contained in:
MatMoul
2026-04-27 23:46:51 +02:00
parent 956cfd7325
commit c56aec350d
1 changed files with 10 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.continue/rules/project.md
+10 -20
View File
@@ -3,30 +3,20 @@ description: mtm-ddwipe project conventions
---
# Project conventions
- Use English throughout the project.
- Keep shell scripts Bash-based.
- Preserve the current behavior of the main script: `mtm-ddwipe` wipes block devices.
- Strengthen destructive-action safety checks in `mtm-ddwipe`.
- Use English.
- Use Bash for shell scripts.
- Keep `mtm-ddwipe` focused on wiping block devices.
- Keep `mtm-ddwipe` interactive by default.
- Require explicit confirmation before destructive actions.
- Validate real block devices and refuse mounted or in-use targets.
- Show clear device details before confirmation.
- Check that target devices are not mounted or in use before wiping.
- Keep user-facing messages short and clear.
- Keep error and help messages short and clear.
- Prefer minimal, focused changes that preserve intent.
- Keep `.continue/rules/project.md` aligned and concise.
- `mtm-ddwipe` is a small Bash script with helper functions.
- Keep the host and line-number removal behavior intact for related output processing.
- `mtm-ddwipe` must print a usage line and support `-h`/`--help`.
- Validate that wipe targets are real block devices before operating on them.
- Keep short, explicit confirmation prompts before destructive operations.
- Prefer confirmation prompts that require typing the target device path or an exact safety phrase.
- Keep help text concise, usage-first, and warning-focused.
- Keep destructive safeguards strict and explicit.
- If adding non-interactive support, make it an opt-in safety flag.
- Keep device identification prompts clear and specific.
- Preserve the fallback wipe flow: secure discard, zero discard, then zero-fill with `dd`.
- Keep timing and status output short and readable.
- Keep messages short and clear.
- Keep help concise, usage-first, and warning-focused.
- Preserve the fallback wipe flow: secure discard, zero discard, then `dd` zero-fill.
- Keep changes minimal and preserve intent.
- Keep `./continue/rules/project.md` aligned and concise.
- If non-interactive support is added, make it an opt-in safety flag.
# Project identity
- Main script: `mtm-ddwipe`