4.8 KiB
Repository Map
High-level map of the repository for contributors and AI agents.
Top Level
Core Bash Tooling
bytelyst-cli.sh- Main CLI entry point for common GitHub operations.
setup.sh- Bootstrap script for installing
pre-commitand local git hooks.
- Bootstrap script for installing
remove_user_interactive.sh- Interactive collaborator removal across matching repositories.
remove_user_guided.sh- Guided UX wrapper for the removal workflow.
remove_user_from_repos.sh- Non-guided removal script.
delete_team_interactive.sh- Interactive team deletion.
make_repos_private.sh- Repository visibility changes.
list_*.sh- Read-oriented listing and reporting utilities.
Supporting Data And Inputs
accounts.example.jsongithub_repos.jsongithub_acc_input.jsonrepos.jsonrepos.txtusers_white_list.jsonusers_black_list.json- account snapshot JSON files in the root
These are operational inputs or snapshots, not general-purpose source files.
Directories
docs/
Canonical onboarding and repo navigation docs.
Current key files:
docs/getting-started.mddocs/repo-map.mddocs/tooling-status.mddocs/supported-scripts.mddocs/operations.mddocs/remove_user_interactive.md
.github/workflows/
Repository automation and validation.
Key files:
pre-commit.ymlshell-validation.yml
git-work-safety-tools/
Scripts for scanning many git repositories and performing safer bulk workflows.
Key files:
git_repos_status.shgit_repos_rebase_commit_push.shmulti_repo_safe_push.shmulti_repo_status.shmulti_repo_interactive_fix.sh
scripts/
Self-contained operational scripts that do not fit the older root-level naming pattern.
Key files:
ubuntu-vm-security-update.shREADME.md
aliases/
Reusable Bash/Zsh alias bundle for common git, tmux, shell, directory, and listing shortcuts.
Key files:
_source_all.aliasinstall.shREADME.md
github_access_scripts/
Focused GitHub access checks.
Key files:
check_repo_access.shlist_user_repos.shREADME.md
github_repo_scanners/
Repo scanning scripts plus generated JSON outputs.
Key files:
create_user_repo_lists.shcreate_contributor_repo_lists.shrun_contributor_json_creation.shuser_repos/contributor_repos/*.json
Slack Message/
Python Slack CLI utility.
Key files:
slack_poster.pyREADME.mdrequirements.txt
youtube/
YouTube transcript and summarization utilities.
Key files:
transcribe_yt_video.pyenhanced_yt_transcript.pysummarize_with_perplexity.pyREADME_youtube_transcripts.mdcaptions/prompts/
supabase monitor/
Separate Python workflow project for YouTube processing. The folder name is misleading; inspect local docs before changing code.
Key files:
README.mdEXECUTION_GUIDE.mdworkflow.pyapi.pyagents/utils/output/
dashboard/
ByteLyst DevOps dashboard — internal product for deployment orchestration and service monitoring.
This is a full ByteLyst product (backend + web) integrated with the common platform:
- Backend: Fastify 5 (port 4004) with platform-service auth, Cosmos DB, deployment orchestration
- Web: Next.js 16 (port 3000) with react-auth, service status cards, deploy buttons
- Integration: Links to/from admin-web, uses @bytelyst/* packages
Key files:
dashboard/backend/src/— Fastify server, services/deployments/health modulesdashboard/web/src/— Next.js app, API client, auth providerdashboard/shared/product.json— Product identity (devops-internal)dashboard/README.md— Setup and usage documentationdashboard/ENDPOINTS.md— Canonical dashboard URL and endpoint inventory
See dashboard/README.md for architecture and setup instructions.
_AZURE/
Account-specific notes and operational docs.
Treat contents as environment-specific documentation rather than core project source.
Legacy Docs
These still exist but are no longer the best starting point:
README_interactive_script.mdREADME_remove_user_script.md
Prefer docs/ for new canonical documentation.
Legacy Root Utilities
These still exist in the repo root but are not the preferred discovery path:
interactive_user_removal.shcleanup.shsync_repos.shtest.shtest_interactive.sh
Treat them as compatibility or one-off helpers unless a canonical doc points to them directly.
Cleanup Guidance
When cleaning this repo:
- do not delete tracked outputs or snapshots unless explicitly asked
- prefer adding orientation docs over moving operational files
- prefer documenting supported entry points over renaming legacy root scripts
- avoid renaming legacy scripts unless you also provide compatibility shims or update all references