{"owner":"dense-analysis","repo":"ale","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# ALE Instructions\n\n## Basic Instructions\n\nRead documentation from @doc/ale-development.txt to understand how to be an\nALE developer and how to match our standards.\n\nRun all tests quickly with `./run-tests -q --fast`, which picks the quickest\nversion of Neovim we can run, and runs our linting checks.\n\nYou can quickly check an individual Vader test file by passing them as arguments\nsuch as `./run-tests -q --fast test/path/some_file.vader`.\n\nYou can quickly run all Lua tests with `./run-tests -q --lua-only`.\n\n\nFor new Vim files, set `Author:` comments to the person doing the work.\nDo not use Codex, OpenAI, or other tool names as the author.\n\n## Writing Tests\n\nFor `test/test-files` they should almost always be 0 bytes in size and files\nmay be marked executable when testing searching for executables.\n"},"files":{"AGENTS.md":"# ALE Instructions\n\n## Basic Instructions\n\nRead documentation from @doc/ale-development.txt to understand how to be an\nALE developer and how to match our standards.\n\nRun all tests quickly with `./run-tests -q --fast`, which picks the quickest\nversion of Neovim we can run, and runs our linting checks.\n\nYou can quickly check an individual Vader test file by passing them as arguments\nsuch as `./run-tests -q --fast test/path/some_file.vader`.\n\nYou can quickly run all Lua tests with `./run-tests -q --lua-only`.\n\n\nFor new Vim files, set `Author:` comments to the person doing the work.\nDo not use Codex, OpenAI, or other tool names as the author.\n\n## Writing Tests\n\nFor `test/test-files` they should almost always be 0 bytes in size and files\nmay be marked executable when testing searching for executables.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# ALE Instructions\n\n## Basic Instructions\n\nRead documentation from @doc/ale-development.txt to understand how to be an\nALE developer and how to match our standards.\n\nRun all tests quickly with `./run-tests -q --fast`, which picks the quickest\nversion of Neovim we can run, and runs our linting checks.\n\nYou can quickly check an individual Vader test file by passing them as arguments\nsuch as `./run-tests -q --fast test/path/some_file.vader`.\n\nYou can quickly run all Lua tests with `./run-tests -q --lua-only`.\n\n\nFor new Vim files, set `Author:` comments to the person doing the work.\nDo not use Codex, OpenAI, or other tool names as the author.\n\n## Writing Tests\n\nFor `test/test-files` they should almost always be 0 bytes in size and files\nmay be marked executable when testing searching for executables.\n","category":"root","tokens":202}]}