{"owner":"openclaw","repo":"gogcli","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Repository Guidelines\n\n## Project Structure\n\n- `cmd/gog/`: CLI entrypoint.\n- `internal/`: implementation (`cmd/`, Google API/OAuth, config/secrets, output/UI).\n- Tests: `*_test.go` next to code; opt-in integration suite in `internal/integration/` (build-tagged).\n- `bin/`: build outputs; `docs/`: specs/releasing; `scripts/`: release helpers + `scripts/gog.mjs`.\n\n## Build, Test, and Development Commands\n\n- `make` / `make build`: build `bin/gog`.\n- `make tools`: install pinned dev tools into `.tools/`.\n- `make fmt` / `make lint` / `make test` / `make ci`: format, lint, test, full local gate.\n- Optional: `pnpm gog …`: build + run in one step.\n- Hooks: `lefthook install` enables pre-commit/pre-push checks.\n\n## Coding Style & Naming Conventions\n\n- Formatting: `make fmt` (`goimports` local prefix `github.com/openclaw/gogcli` + `gofumpt`).\n- Output: keep stdout parseable (`--json` / `--plain`); send human hints/progress to stderr.\n- Gmail labels: treat label IDs as case-sensitive opaque tokens; only case-fold label names for name lookup.\n\n## Testing Guidelines\n\n- Unit tests: stdlib `testing` (and `httptest` where needed).\n- Integration tests (local only):\n  - `GOG_IT_ACCOUNT=you@gmail.com go test -tags=integration ./internal/integration`\n  - Requires OAuth client credentials + a stored refresh token in your keyring.\n\n## Commit & Pull Request Guidelines\n\n- Create commits with `committer \"<msg>\" <file...>`; avoid manual staging.\n- Follow Conventional Commits + action-oriented subjects (e.g. `feat(cli): add --verbose to send`).\n- Group related changes; avoid bundling unrelated refactors.\n- PRs should summarize scope, note testing performed, and mention any user-facing changes or new flags.\n- PR review flow: when given a PR link, review via `gh pr view` / `gh pr diff` and do not change branches.\n\n### PR Workflow (Review vs Land)\n\n- **Review mode (PR link only):** read `gh pr view/diff`; do not switch branches; do not change code.\n- **Landing mode:** temp branch from `main`; bring in PR (squash default; rebase/merge when needed); fix; update `CHANGELOG.md` (PR #/issue + thanks); run `make ci`; final commit; merge to `main`; delete temp; end on `main`.\n- If landing contributor work, always add `Co-authored-by:` trailers for PR authors, even when we partially rewrite, group, or manually apply their changes; leave a PR comment with what landed + SHAs.\n- New contributor: thank in `CHANGELOG.md` (and update README contributors list if present).\n\n## Security & Configuration Tips\n\n- Never commit OAuth client credential JSON files or tokens.\n- Prefer OS keychain backends; use `GOG_KEYRING_BACKEND=file` + `GOG_KEYRING_PASSWORD` only for headless environments.\n"},"files":{"AGENTS.md":"# Repository Guidelines\n\n## Project Structure\n\n- `cmd/gog/`: CLI entrypoint.\n- `internal/`: implementation (`cmd/`, Google API/OAuth, config/secrets, output/UI).\n- Tests: `*_test.go` next to code; opt-in integration suite in `internal/integration/` (build-tagged).\n- `bin/`: build outputs; `docs/`: specs/releasing; `scripts/`: release helpers + `scripts/gog.mjs`.\n\n## Build, Test, and Development Commands\n\n- `make` / `make build`: build `bin/gog`.\n- `make tools`: install pinned dev tools into `.tools/`.\n- `make fmt` / `make lint` / `make test` / `make ci`: format, lint, test, full local gate.\n- Optional: `pnpm gog …`: build + run in one step.\n- Hooks: `lefthook install` enables pre-commit/pre-push checks.\n\n## Coding Style & Naming Conventions\n\n- Formatting: `make fmt` (`goimports` local prefix `github.com/openclaw/gogcli` + `gofumpt`).\n- Output: keep stdout parseable (`--json` / `--plain`); send human hints/progress to stderr.\n- Gmail labels: treat label IDs as case-sensitive opaque tokens; only case-fold label names for name lookup.\n\n## Testing Guidelines\n\n- Unit tests: stdlib `testing` (and `httptest` where needed).\n- Integration tests (local only):\n  - `GOG_IT_ACCOUNT=you@gmail.com go test -tags=integration ./internal/integration`\n  - Requires OAuth client credentials + a stored refresh token in your keyring.\n\n## Commit & Pull Request Guidelines\n\n- Create commits with `committer \"<msg>\" <file...>`; avoid manual staging.\n- Follow Conventional Commits + action-oriented subjects (e.g. `feat(cli): add --verbose to send`).\n- Group related changes; avoid bundling unrelated refactors.\n- PRs should summarize scope, note testing performed, and mention any user-facing changes or new flags.\n- PR review flow: when given a PR link, review via `gh pr view` / `gh pr diff` and do not change branches.\n\n### PR Workflow (Review vs Land)\n\n- **Review mode (PR link only):** read `gh pr view/diff`; do not switch branches; do not change code.\n- **Landing mode:** temp branch from `main`; bring in PR (squash default; rebase/merge when needed); fix; update `CHANGELOG.md` (PR #/issue + thanks); run `make ci`; final commit; merge to `main`; delete temp; end on `main`.\n- If landing contributor work, always add `Co-authored-by:` trailers for PR authors, even when we partially rewrite, group, or manually apply their changes; leave a PR comment with what landed + SHAs.\n- New contributor: thank in `CHANGELOG.md` (and update README contributors list if present).\n\n## Security & Configuration Tips\n\n- Never commit OAuth client credential JSON files or tokens.\n- Prefer OS keychain backends; use `GOG_KEYRING_BACKEND=file` + `GOG_KEYRING_PASSWORD` only for headless environments.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Repository Guidelines\n\n## Project Structure\n\n- `cmd/gog/`: CLI entrypoint.\n- `internal/`: implementation (`cmd/`, Google API/OAuth, config/secrets, output/UI).\n- Tests: `*_test.go` next to code; opt-in integration suite in `internal/integration/` (build-tagged).\n- `bin/`: build outputs; `docs/`: specs/releasing; `scripts/`: release helpers + `scripts/gog.mjs`.\n\n## Build, Test, and Development Commands\n\n- `make` / `make build`: build `bin/gog`.\n- `make tools`: install pinned dev tools into `.tools/`.\n- `make fmt` / `make lint` / `make test` / `make ci`: format, lint, test, full local gate.\n- Optional: `pnpm gog …`: build + run in one step.\n- Hooks: `lefthook install` enables pre-commit/pre-push checks.\n\n## Coding Style & Naming Conventions\n\n- Formatting: `make fmt` (`goimports` local prefix `github.com/openclaw/gogcli` + `gofumpt`).\n- Output: keep stdout parseable (`--json` / `--plain`); send human hints/progress to stderr.\n- Gmail labels: treat label IDs as case-sensitive opaque tokens; only case-fold label names for name lookup.\n\n## Testing Guidelines\n\n- Unit tests: stdlib `testing` (and `httptest` where needed).\n- Integration tests (local only):\n  - `GOG_IT_ACCOUNT=you@gmail.com go test -tags=integration ./internal/integration`\n  - Requires OAuth client credentials + a stored refresh token in your keyring.\n\n## Commit & Pull Request Guidelines\n\n- Create commits with `committer \"<msg>\" <file...>`; avoid manual staging.\n- Follow Conventional Commits + action-oriented subjects (e.g. `feat(cli): add --verbose to send`).\n- Group related changes; avoid bundling unrelated refactors.\n- PRs should summarize scope, note testing performed, and mention any user-facing changes or new flags.\n- PR review flow: when given a PR link, review via `gh pr view` / `gh pr diff` and do not change branches.\n\n### PR Workflow (Review vs Land)\n\n- **Review mode (PR link only):** read `gh pr view/diff`; do not switch branches; do not change code.\n- **Landing mode:** temp branch from `main`; bring in PR (squash default; rebase/merge when needed); fix; update `CHANGELOG.md` (PR #/issue + thanks); run `make ci`; final commit; merge to `main`; delete temp; end on `main`.\n- If landing contributor work, always add `Co-authored-by:` trailers for PR authors, even when we partially rewrite, group, or manually apply their changes; leave a PR comment with what landed + SHAs.\n- New contributor: thank in `CHANGELOG.md` (and update README contributors list if present).\n\n## Security & Configuration Tips\n\n- Never commit OAuth client credential JSON files or tokens.\n- Prefer OS keychain backends; use `GOG_KEYRING_BACKEND=file` + `GOG_KEYRING_PASSWORD` only for headless environments.\n","category":"root","tokens":672}]}