Skip to content

Reorganize repo into category subdirectories#5

Merged
daedalus merged 3 commits intomasterfrom
copilot/reorganize-repo-for-navigability
Feb 21, 2026
Merged

Reorganize repo into category subdirectories#5
daedalus merged 3 commits intomasterfrom
copilot/reorganize-repo-for-navigability

Conversation

Copy link
Contributor

Copilot AI commented Feb 21, 2026

The repo root contained ~180 flat files with no structure, making navigation and discovery difficult. This PR reorganizes everything into logical subdirectories and adds supporting tooling config.

Directory structure

crypto/       # AES, RSA, ECDSA, DH, TOTP, PRNG, hashes
bitcoin/      # Address tools, node scanners, miners, FactorDB
security/     # CVE PoCs, recon, forensics, credential tools
networking/   # DNS, FTP, Docker Swarm, iptables, JSON-RPC
sysadmin/     # Backups, storage, VMs, Android, package setup
math/         # Number theory, ALU, IEEE-754, combinatorics
utils/        # Compression, file tools, data encoding, ML helpers

All moves done via git mv to preserve history. .github/ and examples/ untouched.

Reference fixes

  • security/android_fde_decrypter.sh: updated hardcoded GitHub raw URL pointing to android_fde_decryptkey.py to reflect its new path under security/
  • bitshuffle.py, shuffledata.py, testshuffle.py co-located in utils/ to preserve the local import bitshuffle resolution

Added files

  • README.md — directory layout, usage notes, and DISCLAIMER covering offensive/security tooling (authorized/educational use only)
  • pyproject.toml — black + ruff configuration
  • requirements.txt — third-party dependencies identified by scanning imports across all scripts
  • __init__.py — added to each category dir to support Python package imports
  • .gitignore — excludes __pycache__, .pyc, and build artifacts
Original prompt

Please reorganize the repository daedalus/misc to improve navigability by moving scripts into category subdirectories and updating any references so scripts still work after the move.

Requirements:

  1. Create a categorized folder structure at the repo root (create folders as needed), at minimum:

    • crypto/
    • bitcoin/
    • security/
    • networking/
    • sysadmin/
    • math/
    • utils/
      Keep existing .github/ and examples/ directories intact.
  2. Move existing files from the repo root into the appropriate folders. Use best judgement based on filenames and content.

  3. After moving, update internal references so scripts still work:

    • Fix Python imports that relied on the repo root being on sys.path.
    • Fix relative file path references (open/read/write) if they assumed execution from repo root.
    • If needed, add lightweight package structure (e.g., init.py) to enable imports.
    • Prefer robust solutions (e.g., paths relative to the script file via pathlib) over relying on current working directory.
  4. Add/Update documentation:

    • Add a new README.md at the repo root describing the repo and the new directory layout, with brief usage notes.
    • Add a DISCLAIMER section (either in README.md or as DISCLAIMER.md) covering that some scripts are security/offensive tooling and are for authorized/educational use only.
  5. Naming conventions:

    • Improve naming consistency where reasonable. If renaming files, preserve functionality and update references accordingly.
    • Avoid unnecessary renames that create churn; focus on the most inconsistent or confusing names.
  6. Add a modern Python tooling configuration:

    • Add a pyproject.toml suitable for a scripts repo (not necessarily packaged for PyPI), including at least tool configuration for formatting/linting (e.g., black/ruff) if appropriate.
  7. Add a requirements file:

    • Add requirements.txt capturing common third-party dependencies used by scripts (best-effort by scanning imports). Keep it conservative; avoid listing stdlib modules.
  8. Ensure the repository still functions after reorg:

    • Where feasible, add minimal smoke checks or notes to run key scripts.

Deliverable:

This pull request was created from Copilot chat.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI and others added 2 commits February 21, 2026 19:29
…oml, and requirements.txt

Co-authored-by: daedalus <115175+daedalus@users.noreply.github.com>
Co-authored-by: daedalus <115175+daedalus@users.noreply.github.com>
Copilot AI changed the title [WIP] Reorganize repository structure for improved navigability Reorganize repo into category subdirectories Feb 21, 2026
Copilot AI requested a review from daedalus February 21, 2026 19:31
@daedalus daedalus marked this pull request as ready for review February 21, 2026 19:36
@daedalus daedalus merged commit 4cd6c0a into master Feb 21, 2026
@daedalus daedalus deleted the copilot/reorganize-repo-for-navigability branch February 21, 2026 19:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants