{"owner":"astral-sh","repo":"ty","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":669,"categories":["root-instruction"],"hasMcp":false,"mcpConfig":null,"found":["docs/rules.md","AGENTS.md"],"skills":{"docs/rules.md":"# Rules\n\nRules are individual checks that ty performs to detect common issues in your code, such as\nincompatible assignments, missing imports, or invalid type annotations. Each rule focuses on a\nspecific pattern and can be turned on or off depending on your project’s needs.\n\n!!! tip\n\n    See the [rules reference](./reference/rules.md) for an enumeration of all supported rules.\n\n## Rule levels\n\nEach rule has a configurable level:\n\n- `error`: violations are reported as errors and ty exits with an exit code of 1 if there's any.\n- `warn`: violations are reported as warnings. By default, ty exits with code `1` if there are only\n    warning-level violations. Use `--exit-zero-on-warning` or set `terminal.error-on-warning` to\n    `false` to exit with code `0` instead.\n- `ignore`: the rule is turned off\n\nYou can configure the level for each rule on the command line using the `--warn`, `--error`, and\n`--ignore` flags. For example:\n\n```shell\n\nty check \\\n  --warn unused-ignore-comment \\        # Make `unused-ignore-comment` a warning\n  --ignore redundant-cast \\             # Disable `redundant-cast`\n  --error possibly-missing-attribute \\  # Error on `possibly-missing-attribute`\n  --error possibly-missing-import       # Error on `possibly-missing-import`\n```\n\nThe options can be repeated. Subsequent options override earlier options.\n\nRule levels can also be changed in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\nYou can also configure the level for all rules at once.\n\nOn the command line you can use `--error all`, `--warn all`, or `--ignore all`. For example:\n\n```shell\n\nty check --error all\n```\n\nYou can also configure this setting in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    all = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    all = \"error\"\n    ```\n","AGENTS.md":"# ty Repository\n\n## Security reviews\n\nFor reviews of this repository's GitHub automation, CI, and release process, use the [GitHub repository threat model](agents/references/repository-threat-model.md). The `ruff` submodule pins ty's Rust source for release builds; include it when tracing the source of release artifacts.\n"},"files":{"docs/rules.md":"# Rules\n\nRules are individual checks that ty performs to detect common issues in your code, such as\nincompatible assignments, missing imports, or invalid type annotations. Each rule focuses on a\nspecific pattern and can be turned on or off depending on your project’s needs.\n\n!!! tip\n\n    See the [rules reference](./reference/rules.md) for an enumeration of all supported rules.\n\n## Rule levels\n\nEach rule has a configurable level:\n\n- `error`: violations are reported as errors and ty exits with an exit code of 1 if there's any.\n- `warn`: violations are reported as warnings. By default, ty exits with code `1` if there are only\n    warning-level violations. Use `--exit-zero-on-warning` or set `terminal.error-on-warning` to\n    `false` to exit with code `0` instead.\n- `ignore`: the rule is turned off\n\nYou can configure the level for each rule on the command line using the `--warn`, `--error`, and\n`--ignore` flags. For example:\n\n```shell\n\nty check \\\n  --warn unused-ignore-comment \\        # Make `unused-ignore-comment` a warning\n  --ignore redundant-cast \\             # Disable `redundant-cast`\n  --error possibly-missing-attribute \\  # Error on `possibly-missing-attribute`\n  --error possibly-missing-import       # Error on `possibly-missing-import`\n```\n\nThe options can be repeated. Subsequent options override earlier options.\n\nRule levels can also be changed in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\nYou can also configure the level for all rules at once.\n\nOn the command line you can use `--error all`, `--warn all`, or `--ignore all`. For example:\n\n```shell\n\nty check --error all\n```\n\nYou can also configure this setting in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    all = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    all = \"error\"\n    ```\n","AGENTS.md":"# ty Repository\n\n## Security reviews\n\nFor reviews of this repository's GitHub automation, CI, and release process, use the [GitHub repository threat model](agents/references/repository-threat-model.md). The `ruff` submodule pins ty's Rust source for release builds; include it when tracing the source of release artifacts.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/astral-sh/ty/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# ty Repository\n\n## Security reviews\n\nFor reviews of this repository's GitHub automation, CI, and release process, use the [GitHub repository threat model](agents/references/repository-threat-model.md). The `ruff` submodule pins ty's Rust source for release builds; include it when tracing the source of release artifacts.\n","isInternal":false,"tokens":64,"sizeBytes":323},{"name":"rules.md","path":"docs/rules.md","rawUrl":"https://raw.githubusercontent.com/astral-sh/ty/HEAD/docs/rules.md","title":"docs - Development & Architecture Rules","category":"root-instruction","format":"markdown","content":"# Rules\n\nRules are individual checks that ty performs to detect common issues in your code, such as\nincompatible assignments, missing imports, or invalid type annotations. Each rule focuses on a\nspecific pattern and can be turned on or off depending on your project’s needs.\n\n!!! tip\n\n    See the [rules reference](./reference/rules.md) for an enumeration of all supported rules.\n\n## Rule levels\n\nEach rule has a configurable level:\n\n- `error`: violations are reported as errors and ty exits with an exit code of 1 if there's any.\n- `warn`: violations are reported as warnings. By default, ty exits with code `1` if there are only\n    warning-level violations. Use `--exit-zero-on-warning` or set `terminal.error-on-warning` to\n    `false` to exit with code `0` instead.\n- `ignore`: the rule is turned off\n\nYou can configure the level for each rule on the command line using the `--warn`, `--error`, and\n`--ignore` flags. For example:\n\n```shell\n\nty check \\\n  --warn unused-ignore-comment \\        # Make `unused-ignore-comment` a warning\n  --ignore redundant-cast \\             # Disable `redundant-cast`\n  --error possibly-missing-attribute \\  # Error on `possibly-missing-attribute`\n  --error possibly-missing-import       # Error on `possibly-missing-import`\n```\n\nThe options can be repeated. Subsequent options override earlier options.\n\nRule levels can also be changed in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\nYou can also configure the level for all rules at once.\n\nOn the command line you can use `--error all`, `--warn all`, or `--ignore all`. For example:\n\n```shell\n\nty check --error all\n```\n\nYou can also configure this setting in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    all = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    all = \"error\"\n    ```\n","isInternal":false,"tokens":605,"sizeBytes":2490}],"systemPromptSnippet":"<yakaai_skills repo=\"astral-sh/ty\">\n<!-- File: AGENTS.md (Tokens: ~64 | Category: root-instruction) -->\n# ty Repository\n\n## Security reviews\n\nFor reviews of this repository's GitHub automation, CI, and release process, use the [GitHub repository threat model](agents/references/repository-threat-model.md). The `ruff` submodule pins ty's Rust source for release builds; include it when tracing the source of release artifacts.\n\n<!-- File: docs/rules.md (Tokens: ~605 | Category: root-instruction) -->\n# Rules\n\nRules are individual checks that ty performs to detect common issues in your code, such as\nincompatible assignments, missing imports, or invalid type annotations. Each rule focuses on a\nspecific pattern and can be turned on or off depending on your project’s needs.\n\n!!! tip\n\n    See the [rules reference](./reference/rules.md) for an enumeration of all supported rules.\n\n## Rule levels\n\nEach rule has a configurable level:\n\n- `error`: violations are reported as errors and ty exits with an exit code of 1 if there's any.\n- `warn`: violations are reported as warnings. By default, ty exits with code `1` if there are only\n    warning-level violations. Use `--exit-zero-on-warning` or set `terminal.error-on-warning` to\n    `false` to exit with code `0` instead.\n- `ignore`: the rule is turned off\n\nYou can configure the level for each rule on the command line using the `--warn`, `--error`, and\n`--ignore` flags. For example:\n\n```shell\n\nty check \\\n  --warn unused-ignore-comment \\        # Make `unused-ignore-comment` a warning\n  --ignore redundant-cast \\             # Disable `redundant-cast`\n  --error possibly-missing-attribute \\  # Error on `possibly-missing-attribute`\n  --error possibly-missing-import       # Error on `possibly-missing-import`\n```\n\nThe options can be repeated. Subsequent options override earlier options.\n\nRule levels can also be changed in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    unused-ignore-comment = \"warn\"\n    redundant-cast = \"ignore\"\n    possibly-missing-attribute = \"error\"\n    possibly-missing-import = \"error\"\n    ```\n\nYou can also configure the level for all rules at once.\n\nOn the command line you can use `--error all`, `--warn all`, or `--ignore all`. For example:\n\n```shell\n\nty check --error all\n```\n\nYou can also configure this setting in the [`rules`](./reference/configuration.md#rules) section of a\n[configuration file](./configuration.md).\n\nFor example, the following is equivalent to the command above:\n\n=== \"pyproject.toml\"\n\n    ```toml\n    [tool.ty.rules]\n    all = \"error\"\n    ```\n\n=== \"ty.toml\"\n\n    ```toml\n    [rules]\n    all = \"error\"\n    ```\n</yakaai_skills>"}