Michael Chus
0005f3e41a
The always-on set is paid by every session, so it gets the tightest form: git-sync-check shrinks to its procedural core, testing-policy moves the table-test example to README.md and folds the agent instructions into the rules, go-code-style inlines the error-wrapping example. Per-session read cost drops from 403 to 336 lines. Also restore the pagination response fields in table-management: the previous dedup replaced them with a reference to go-api, which the table router line does not load. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
779 B
779 B
Git Sync Check
Rule
Before starting any work on a task (repositories are hosted in Gitea):
git fetch origingit log HEAD..@{u} --oneline- Non-empty output: stop immediately, make no changes, tell the user the remote has new commits and ask how to proceed (pull, rebase, ignore).
- Empty output: proceed normally.
If offline and fetch is impossible: notify the user before proceeding. Web UI inspection does not replace the local check.
Gitea Workflow
- Create a task branch before changes (
git checkout -b <branch>), push withgit push -u origin <branch>, review via a Gitea pull request (theteaCLI may be used if configured). - Do not assume GitHub tooling such as
gh; do not use GitLab terminology such asmerge request.