Repository cleanup and reorganization

Open

#172 opened on Jul 9, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 15/100

Issue type: Refactor
Clarity: Needs clarification
Activity status: Stale
Tech stack: git, shell
Domain: documentation, tooling

Research direction

Review index.md, GIT_SETUP_GUIDE.md, the .claude/ directory, and the reorganized scripts/active/, scripts/archive/, and scripts/examples/ paths. Compare them with the cleanup described in the issue; done means the documentation hierarchy and script organization match the stated structure without the listed redundant files.

Written by the indexing model from the issue text.

Description

Summary

Performed comprehensive cleanup of the dotfiles repository, removing redundant files and reorganizing documentation.

Work Completed

Markdown Cleanup

Analyzed 32 markdown files for redundancy
Removed obsolete documentation:
- PROJECT_DASHBOARD.md
- go-blocksite/README.md
- karabiner/README.md
- jira/README.md
- git/docs/github-issues/*.md
Consolidated git documentation from 5 files into GIT_SETUP_GUIDE.md

Shell Script Analysis

Analyzed 22 shell scripts
Removed 6 redundant scripts
Merged git/setup.sh into install.sh
Reorganized into logical structure:
- scripts/active/nix-darwin/
- scripts/active/tmux/
- scripts/archive/
- scripts/examples/

Documentation Structure

Created .claude/ directory for AI context
Moved PROJECT.md to .claude/ and generalized content
Created comprehensive index.md
Established clear documentation hierarchy

Improvement Ideas Documented

Common patterns for abstraction
Security vulnerabilities identified
Cross-platform compatibility issues
Performance improvements noted
Nix-Darwin integration opportunities

Files Removed

Approximately 15 redundant files removed
Old command and context directories cleaned up
Legacy documentation consolidated or removed

Dominant language: Jupyter Notebook
Stars: 1
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Don't recommend a sunset code editor (Atom) Open

Difficulty 1/5 Under an hour Newbie friendliness 95/100

Git-it-App/git-it-electron#1047 · Opened Sep 24, 2026
Duplicated 'Connect to Database Using C#' link in Postgres Tutorial Page Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

neondatabase/website#5944 · Opened Sep 24, 2026
Pagination: Give the generated composed-link example contextual names Open

📕documentation

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

db-ux-design-system/core-web#8239 · Opened Sep 24, 2026
Feedback on page https://wiki.libsdl.org/wiki/search Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

libsdl-org/sdlwiki#1008 · Opened Sep 24, 2026
Dedicated workers seem to already inherit permissions policuy Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

explainers-by-googlers/workers-permissions-policy#5 · Opened Sep 24, 2026