the signals and their derived score are provisional and subject to change.
validate manually before sharing.
7351a808ff5d7df109fea3da37329562efda0a40182554d9a3523 months agoCo-authored-by: Claude Opus 4.8 <noreply@anthropic.com>7579fb19d6f23 months agoCo-authored-by: Claude Opus 4.8 <noreply@anthropic.com>604df13910cd3 months agoCo-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>bad3eac886f54 months agoCo-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>2121fb6e13b64 months agoCo-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>3fb3402da6664 months agoCo-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>875928835c6f4 months agoCo-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>7a00ba532b1b4 months agoCo-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>0abf022ca4cf4 months agoCo-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com># Working in this repo
## Workflow rules
- **Always work in a git worktree on a feature branch.** Never edit files
while the primary checkout sits on `main`. Use
`git worktree add ../forgejo-cli-<topic> -b feature/<topic>` (or use the
`superpowers:using-git-worktrees` skill).
- **No commits directly to `main`.** `main` is reachable only by merging a
PR. Server-side branch protection (if configured) enforces this; client-
side, never push to `main` and never commit while checked out on `main`.
- none