skynet/claude-foundations
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

CLAUDE.md: add Gitea CI visibility section pointing at gitea-agent-companion (gac --help)

Browse Source
This commit is contained in:
Paul O'Reilly
2026-07-07 17:52:19 +12:00
parent d547fe08e0
commit b41677f831
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CLAUDE.md
View File

@@ -63,6 +63,10 @@ Then proceed directly to step 2. Otherwise:
- When a task requires a secret, read it at execution time from the secrets folder and use it ephemerally. Do not cache or persist the value. - When a task requires a secret, read it at execution time from the secrets folder and use it ephemerally. Do not cache or persist the value.
- Referencing the **existence** of a secret file is fine (e.g., "credentials are in `~/dev/claude/secrets/gitea/ai_enablement`") — referencing the contents is not. - Referencing the **existence** of a secret file is fine (e.g., "credentials are in `~/dev/claude/secrets/gitea/ai_enablement`") — referencing the contents is not.
## Gitea CI visibility
When working with Gitea (watching Actions runs, checking whether a release/container built, diagnosing failing CI), use `gitea-agent-companion` — alias `gac`, installed in `~/sbin`, source at `projects/gitea-agent-companion`. Run `gitea-agent-companion --help` first: the help text is the full reference (verbs, flags, token discovery, exit codes). Canonical post-push pattern: `gac tail <owner/repo> --until run-complete --timeout 600`; on failure, `gac inspect <owner/repo> --run <N> --logs`.
## Process Principles ## Process Principles
Hard-won lessons that apply across every project: Hard-won lessons that apply across every project: