How dhetchaiyakrith24/smogz-rules works
smogz-rules maintains one canonical set of shared rules and distributes copies to configured project repositories. The workflow is: an owner authorizes a change, maintainers update the canonical rules through a PR, the guard checks them, and after merge the sync automation opens copy PRs for target repositories. Separate automation checks the sync token and reports expiry risk. Relationships below follow the README; source excerpts were unavailable, so implementation details beyond documented behavior are omitted.
Main entry points: sync.sh Copy sync · guard.sh Guard check · token-check.yml Token check · sync.yml Sync workflow
Components 15
Canonical rules
- Canonical rules
CLAUDE.md
Validation and tokens
- Project-only words
guard/project-only-words.txt - Guard check
scripts/guard.sh - Guard workflow
.github/workflows/guard.yml - Token check
.github/workflows/token-check.yml
Copy distribution
- Target repositories
targets.txt - Copy sync
scripts/sync.sh - Sync workflow
.github/workflows/sync.yml
Other components
- Rule owner
- Repository maintainers
- GitHub Actions
- Sync token
- Destination repositories
- Copy pull requests
- Failure issues
Connections 17
- Rule owner → Repository maintainers: authorizes changes
- Repository maintainers → Canonical rules: edits via PR
- GitHub Actions → Guard workflow: runs
- Guard workflow → Guard check: invokes
- Guard check → Canonical rules: checks
- Guard check → Project-only words: reads
- GitHub Actions → Sync workflow: runs
- Sync workflow → Copy sync: invokes
- Copy sync → Canonical rules: copies
- Copy sync → Target repositories: reads
- Copy sync → Sync token: uses
- Copy sync → Destination repositories: updates
- Copy sync → Copy pull requests: opens
- GitHub Actions → Token check: runs weekly
- Token check → Sync token: checks validity
- Token check → Failure issues: reports expiry
- Sync workflow → Failure issues: reports failure