{"owner":"grafana","repo":"loki","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\nInstructions file for coding agents.\n\n## Environment Setup\n\n- Use the minimum Go version specified in [go.mod](go.mod)\n- Warn the user about an old Go version\n- The project uses GNU make for building binaries and images. See [Makefile](Makefile)\n\n## Commands\n\n### Tests\n\nFor fast feeback run tests using `go test` (or `gotest` if available).\n\n```bash\ngo test -v ./...                               # run all tests with Go directly\ngo test -v ./pkg/...                           # run Loki package tests\ngo test -v ./pkg/<pkg>/...                     # run tests in specific package\ngo test -v -test.run TestName ./pkg/<pkg>/...  # run a specific test\n```\n\nFor full verification use dedicated `make` targets (only when requested).\n\n```\nmake test                                      # run full test suite\nmake test-integration                          # run integration test suite\nmake test-fuzz                                 # run fuzz tests\n```\n\n## Code Style\n\n- Follow standard Go formatting (gofmt/goimports)\n- Follow import order:\n  1. standard lib\n  2. external packages\n  3. Loki packages (`github.com/grafana/loki/v3`)\n- Error handling: Always check errors with `if err != nil { return ... }`\n- Use structured logging with leveled logging (`github.com/go-kit/log`)\n- Document all exported functions, types, and variables\n\n### Testing\n\n- Always prefer `github.com/stretchr/testify/require` over `github.com/stretchr/testify/assert`\n- Use table-driven tests when appropriate\n\n## Commits and Pull Requests\n\n- Always run Loki package tests `gotest -v ./pkg/...` before commiting\n- Focus on \"why\", rather than \"what\" in the commit message and PR description\n- Follow conventional commits format: `<type>(<scope>): Your change` (note the uppercase after colon)\n\n## Documentation Standards\n\n- Follow the Grafana [Writers' Toolkit](https://grafana.com/docs/writers-toolkit/) Style Guide\n- Use CommonMark flavor of markdown for documentation\n- Create LIDs (Loki Improvement Documents) for large functionality changes\n- Document upgrading steps in `docs/sources/setup/upgrade/_index.md`\n- Preview docs locally with `make docs` from the `/docs` directory\n- Include examples and clear descriptions for public APIs\n\n## Using Tools\n\n- When using the `mcp__acp__Write` tool, write to a path within the current worktree to avoid sandboxing/permissions issues. This includes when writing plan files.\n"},"files":{"AGENTS.md":"# AGENTS.md\n\nInstructions file for coding agents.\n\n## Environment Setup\n\n- Use the minimum Go version specified in [go.mod](go.mod)\n- Warn the user about an old Go version\n- The project uses GNU make for building binaries and images. See [Makefile](Makefile)\n\n## Commands\n\n### Tests\n\nFor fast feeback run tests using `go test` (or `gotest` if available).\n\n```bash\ngo test -v ./...                               # run all tests with Go directly\ngo test -v ./pkg/...                           # run Loki package tests\ngo test -v ./pkg/<pkg>/...                     # run tests in specific package\ngo test -v -test.run TestName ./pkg/<pkg>/...  # run a specific test\n```\n\nFor full verification use dedicated `make` targets (only when requested).\n\n```\nmake test                                      # run full test suite\nmake test-integration                          # run integration test suite\nmake test-fuzz                                 # run fuzz tests\n```\n\n## Code Style\n\n- Follow standard Go formatting (gofmt/goimports)\n- Follow import order:\n  1. standard lib\n  2. external packages\n  3. Loki packages (`github.com/grafana/loki/v3`)\n- Error handling: Always check errors with `if err != nil { return ... }`\n- Use structured logging with leveled logging (`github.com/go-kit/log`)\n- Document all exported functions, types, and variables\n\n### Testing\n\n- Always prefer `github.com/stretchr/testify/require` over `github.com/stretchr/testify/assert`\n- Use table-driven tests when appropriate\n\n## Commits and Pull Requests\n\n- Always run Loki package tests `gotest -v ./pkg/...` before commiting\n- Focus on \"why\", rather than \"what\" in the commit message and PR description\n- Follow conventional commits format: `<type>(<scope>): Your change` (note the uppercase after colon)\n\n## Documentation Standards\n\n- Follow the Grafana [Writers' Toolkit](https://grafana.com/docs/writers-toolkit/) Style Guide\n- Use CommonMark flavor of markdown for documentation\n- Create LIDs (Loki Improvement Documents) for large functionality changes\n- Document upgrading steps in `docs/sources/setup/upgrade/_index.md`\n- Preview docs locally with `make docs` from the `/docs` directory\n- Include examples and clear descriptions for public APIs\n\n## Using Tools\n\n- When using the `mcp__acp__Write` tool, write to a path within the current worktree to avoid sandboxing/permissions issues. This includes when writing plan files.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md\n\nInstructions file for coding agents.\n\n## Environment Setup\n\n- Use the minimum Go version specified in [go.mod](go.mod)\n- Warn the user about an old Go version\n- The project uses GNU make for building binaries and images. See [Makefile](Makefile)\n\n## Commands\n\n### Tests\n\nFor fast feeback run tests using `go test` (or `gotest` if available).\n\n```bash\ngo test -v ./...                               # run all tests with Go directly\ngo test -v ./pkg/...                           # run Loki package tests\ngo test -v ./pkg/<pkg>/...                     # run tests in specific package\ngo test -v -test.run TestName ./pkg/<pkg>/...  # run a specific test\n```\n\nFor full verification use dedicated `make` targets (only when requested).\n\n```\nmake test                                      # run full test suite\nmake test-integration                          # run integration test suite\nmake test-fuzz                                 # run fuzz tests\n```\n\n## Code Style\n\n- Follow standard Go formatting (gofmt/goimports)\n- Follow import order:\n  1. standard lib\n  2. external packages\n  3. Loki packages (`github.com/grafana/loki/v3`)\n- Error handling: Always check errors with `if err != nil { return ... }`\n- Use structured logging with leveled logging (`github.com/go-kit/log`)\n- Document all exported functions, types, and variables\n\n### Testing\n\n- Always prefer `github.com/stretchr/testify/require` over `github.com/stretchr/testify/assert`\n- Use table-driven tests when appropriate\n\n## Commits and Pull Requests\n\n- Always run Loki package tests `gotest -v ./pkg/...` before commiting\n- Focus on \"why\", rather than \"what\" in the commit message and PR description\n- Follow conventional commits format: `<type>(<scope>): Your change` (note the uppercase after colon)\n\n## Documentation Standards\n\n- Follow the Grafana [Writers' Toolkit](https://grafana.com/docs/writers-toolkit/) Style Guide\n- Use CommonMark flavor of markdown for documentation\n- Create LIDs (Loki Improvement Documents) for large functionality changes\n- Document upgrading steps in `docs/sources/setup/upgrade/_index.md`\n- Preview docs locally with `make docs` from the `/docs` directory\n- Include examples and clear descriptions for public APIs\n\n## Using Tools\n\n- When using the `mcp__acp__Write` tool, write to a path within the current worktree to avoid sandboxing/permissions issues. This includes when writing plan files.\n","category":"root","tokens":602}]}