core-labs/core
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

docs: update bootstrap skill and add git-forgejo config doc per new rules

Browse source
This commit is contained in:
Shay 2026-07-05 14:24:13 -07:00
parent 27a620d694
commit 19ce7fa0e6
2 changed files with 29 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
docs/dev/git-forgejo.md Normal file
View file

@ -0,0 +1,24 @@
# Git + Forgejo Setup (replaces GitHub CLI)
We do **not** use the `gh` (GitHub CLI) tool.
All Git operations use plain `git`, with remotes transparently forwarded to our self-hosted Forgejo instance via `insteadOf` configuration.
## Required global config
```bash
git config --global url."ssh://git@core-gitquarters.acbcontent.org:29222/core-labs/".insteadOf "git@github.com:core-labs/"
git config --global url."https://core-gitquarters.acbcontent.org/core-labs/".insteadOf "https://github.com/core-labs/"
git config --global url."ssh://git@core-gitquarters.acbcontent.org:29222/AssetOverflow/".insteadOf "git@github.com:AssetOverflow/"
git config --global url."https://core-gitquarters.acbcontent.org/AssetOverflow/".insteadOf "https://github.com/AssetOverflow/"
```
## Usage
- Clone, fetch, push, etc. with normal `git` commands (e.g. `git push -u origin main`).
- The above rules rewrite `git@github.com:AssetOverflow/core.git` etc. to the Forgejo SSH/HTTPS endpoints.
- For PRs, reviews, and issue management: use the Forgejo web UI at https://core-gitquarters.acbcontent.org/forgejo_admin/core
See AGENTS.md for full workflow rules, branch hygiene, and commit/PR guidelines.
This setup is mandatory for all contributors and agents.

8
skills/core-bootstrap.md
View file

@ -5,7 +5,9 @@ triggers: ["session_start", "new_subagent", "arena_spawn"]
auto_invoke: true auto_invoke: true
--- ---
Execute the full **Session Start Checklist** from GROK.md in strict order, including the **Workspace Hygiene + Branch/Worktree Protocol**: Execute the full **Session Start Checklist** from GROK.md in strict order, including the **Workspace Hygiene + Branch/Worktree Protocol**.
**Important:** We use plain `git` (with insteadOf forwarding to Forgejo) and never `gh`. See AGENTS.md and `docs/dev/git-forgejo.md` for the required global config and setup.
1. Read GROK.md in full. 1. Read GROK.md in full.
2. Read AGENTS.md in full. 2. Read AGENTS.md in full.
@ -31,8 +33,8 @@ Execute the full **Session Start Checklist** from GROK.md in strict order, inclu
10. Run `core test --suite smoke -q` and report pass/fail. If unavailable, report the exact failure and use repo-native pytest lanes. 10. Run `core test --suite smoke -q` and report pass/fail. If unavailable, report the exact failure and use repo-native pytest lanes.
11. Check for and read any `HANDOFF-*-YYYY-MM-DD.md` from the last 3 days. 11. Check for and read any `HANDOFF-*-YYYY-MM-DD.md` from the last 3 days.
12. Check recent open PRs if local changes or task continuity are ambiguous: 12. Check recent open PRs if local changes or task continuity are ambiguous:
- `gh pr list --state open --limit 20` - Use the Forgejo web UI: https://core-gitquarters.acbcontent.org/forgejo_admin/core/pulls
- `gh pr status` - Or `git fetch origin --prune && git branch -r | head -20` for remote branches.
13. State task scope in one clear sentence before any further action. 13. State task scope in one clear sentence before any further action.
This skill must complete successfully before any editing, proposal, or subagent work. It is non-bypassable for Grok 4.3 / Grok Build sessions on CORE. This skill must complete successfully before any editing, proposal, or subagent work. It is non-bypassable for Grok 4.3 / Grok Build sessions on CORE.