Add a Work Tracking entry to README Primary Entry Points and a short pointer in CLAUDE.md, both routing to scripts/tracker-seed/ and the AGENTS.md section. Generated with [Devin](https://cli.devin.ai/docs) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
1.8 KiB
1.8 KiB
CLAUDE.md
Claude-specific working notes for this repository.
Read First
Use these as the canonical orientation docs:
README.mddocs/getting-started.mddocs/repo-map.mddocs/tooling-status.mdscripts/README.mdAGENTS.md
This file is intentionally short and should not become a second full repo README.
Repository Shape
The repo is a mixed workspace:
- root Bash scripts for GitHub administration and maintenance
git-work-safety-tools/for multi-repo git workflowsgithub_access_scripts/andgithub_repo_scanners/for access scanning- self-contained Python utilities in
Slack Message/,youtube/, andsupabase monitor/
Do not assume a single dependency graph or runtime model across the whole repo.
High-Value Files
bytelyst-cli.shremove_user_interactive.shremove_user_guided.shremove_user_from_repos.shgit-work-safety-tools/*.sh
Cutting Tracker Items
When asked to "cut items to track", use scripts/tracker-seed/ (seeds the
ByteLyst tracker via platform-service POST /api/items). Do not hand-roll API
calls. Full procedure is in the "Cutting Tracker Items" section of AGENTS.md.
Safety Notes
- Treat
accounts.json, account snapshot JSON files,.envfiles, and generated contributor/output data as sensitive. - Avoid echoing secret-bearing file contents unless the task requires it.
- Many scripts are operational and potentially destructive. Preserve prompts, dry-run behavior, and confirmations unless asked to change them.
Developer Commands
./setup.sh
pre-commit run --all-files
./test.sh
Documentation Rule
If you change repo structure, onboarding, or navigation, update:
README.mddocs/repo-map.mddocs/tooling-status.mdAGENTS.mdif agent navigation is affected