{"owner":"primer","repo":"octicons","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":1145,"categories":["root-instruction","anthropic-skill"],"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md",".github/skills/changesets/SKILL.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\n## Running tasks\n\n- Prefer running repository tasks through Turborepo from the repository root, for example `npx turbo run build`.\n- When targeting a specific workspace, use `--filter` with its package name, for example `npx turbo run build --filter=@primer/octicons-react`.\n\n## Adding and reviewing octicons\n\n- Follow the [add-octicon checklist](docs/add-octicon-checklist.md) when adding or reviewing octicons.\n- When reviewing a pull request that adds, updates, or renames an Octicon, load and follow `.github/skills/icon-request-review/SKILL.md`. Use its contribution review phase and load only the references that phase requires.\n- Treat a pull request as an Octicon contribution when its stated purpose or diff includes icon source files, icon naming or compatibility metadata, icon keywords, or generated icon exports and snapshots. Do not load the skill for an unrelated change merely because it touches shared build or release infrastructure.\n",".github/skills/changesets/SKILL.md":"---\nname: changesets\ndescription: \"Use when a pull request changes a package's public API. Covers affected packages, semantic version impact, file format, and user-focused release notes.\"\n---\n\n# Changesets\n\nThis repository uses [Changesets](https://github.com/changesets/changesets) to\nversion packages and generate changelogs. Add a changeset whenever a pull\nrequest changes the public API of a published package.\n\nA changeset records:\n\n1. Every published package affected by the public API change\n2. The semantic version impact (`patch`, `minor`, or `major`) for each package\n3. A concise description of the change for users of the affected packages\n\n## When a changeset is required\n\nAdd a changeset for consumer-facing changes such as:\n\n- Adding, removing, or renaming an icon\n- Changing an icon's rendered appearance or behavior\n- Adding, removing, or changing an export\n- Changing public JavaScript, React, CSS, or TypeScript APIs\n- Fixing behavior that users experience through a package's public API\n\nChanges that do not affect a published package's public API, such as\ndocumentation, tests, internal refactors, or CI configuration, do not need a\nchangeset. Add the `skip changeset` label to those pull requests.\n\n## Identify affected packages\n\nReview the change from the perspective of users of each package. For a new\nicon, select all npm packages whose generated public APIs change:\n\n- `@primer/octicons`\n- `@primer/octicons-react`\n- `@primer/octicons-react-symbols`\n- `@primer/styled-octicons`\n\nDo not select a package only because its internal source or build process\nchanged. Select it when users of that package will observe the change.\n\nEvery new icon adds a public export to all four npm packages, so select `minor`\nfor all four. `@primer/octicons-react-symbols` keeps an independent `0.x`\nversion and sits outside the linked release group, so select it explicitly.\nDo not add it to the linked group while it has an independent version line:\nChangesets versions linked releases from the highest current version in the\ngroup.\n\nThe Changesets workspace graph adds `octicons_gem`, `octicons_helper`, and\n`jekyll-octicons` to a shared icon-data release. Confirm that the changeset bot\nlists them, but do not select them solely because shared icon data changed.\nSelect a Ruby workspace directly when the pull request makes a Ruby-specific\npublic change.\n\n## Choose the version impact\n\n- `patch`: A backwards-compatible fix to existing public behavior or icon\n  output\n- `minor`: A backwards-compatible public API addition, such as a new icon or\n  export, or a canonical rename that preserves the old name as a compatibility\n  alias\n- `major`: A breaking public API change, such as removing or renaming an icon\n  or export without backwards compatibility\n\nChoose the impact independently for each affected package.\n\n## Author a changeset\n\nRun `npx changeset` and follow the prompts to select every affected package,\nchoose its version impact, and enter the description. Commit the generated\nmarkdown file in `.changeset/` to the pull request branch.\n\nUse one changeset for one user-facing change. Do not add a second changeset for\ngenerated files, snapshots, or a follow-up that only completes the same public\nAPI change.\n\nTo create one manually, add a uniquely named markdown file in `.changeset/`\nwith YAML frontmatter for all affected packages:\n\n```markdown\n---\n'@primer/octicons': minor\n'@primer/octicons-react': minor\n'@primer/octicons-react-symbols': minor\n'@primer/styled-octicons': minor\n---\n\nAdd the accessibility icon for representing accessible experiences.\n```\n\n## Write for package users\n\nThe description is published in package changelogs and release notes. Write it\nas communication to users of the library:\n\n- Describe the public API change and its user-visible effect\n- Use one or two concise sentences\n- Name relevant icons, exports, or packages when that helps users understand\n  the impact\n- Use present tense and active voice\n- Exclude implementation details, internal file names, test changes, and pull\n  request process\n\nGood:\n\n```markdown\nAdd the `AccessibilityInsetIcon` export for representing accessible\nexperiences.\n```\n\nAvoid:\n\n```markdown\nUpdate the build script and generated files after adding a new SVG, including\nsnapshot changes.\n```\n\nThe avoided example explains the implementation rather than the public API\nchange that users need to know about.\n"},"files":{"AGENTS.md":"# AGENTS.md\n\n## Running tasks\n\n- Prefer running repository tasks through Turborepo from the repository root, for example `npx turbo run build`.\n- When targeting a specific workspace, use `--filter` with its package name, for example `npx turbo run build --filter=@primer/octicons-react`.\n\n## Adding and reviewing octicons\n\n- Follow the [add-octicon checklist](docs/add-octicon-checklist.md) when adding or reviewing octicons.\n- When reviewing a pull request that adds, updates, or renames an Octicon, load and follow `.github/skills/icon-request-review/SKILL.md`. Use its contribution review phase and load only the references that phase requires.\n- Treat a pull request as an Octicon contribution when its stated purpose or diff includes icon source files, icon naming or compatibility metadata, icon keywords, or generated icon exports and snapshots. Do not load the skill for an unrelated change merely because it touches shared build or release infrastructure.\n",".github/skills/changesets/SKILL.md":"---\nname: changesets\ndescription: \"Use when a pull request changes a package's public API. Covers affected packages, semantic version impact, file format, and user-focused release notes.\"\n---\n\n# Changesets\n\nThis repository uses [Changesets](https://github.com/changesets/changesets) to\nversion packages and generate changelogs. Add a changeset whenever a pull\nrequest changes the public API of a published package.\n\nA changeset records:\n\n1. Every published package affected by the public API change\n2. The semantic version impact (`patch`, `minor`, or `major`) for each package\n3. A concise description of the change for users of the affected packages\n\n## When a changeset is required\n\nAdd a changeset for consumer-facing changes such as:\n\n- Adding, removing, or renaming an icon\n- Changing an icon's rendered appearance or behavior\n- Adding, removing, or changing an export\n- Changing public JavaScript, React, CSS, or TypeScript APIs\n- Fixing behavior that users experience through a package's public API\n\nChanges that do not affect a published package's public API, such as\ndocumentation, tests, internal refactors, or CI configuration, do not need a\nchangeset. Add the `skip changeset` label to those pull requests.\n\n## Identify affected packages\n\nReview the change from the perspective of users of each package. For a new\nicon, select all npm packages whose generated public APIs change:\n\n- `@primer/octicons`\n- `@primer/octicons-react`\n- `@primer/octicons-react-symbols`\n- `@primer/styled-octicons`\n\nDo not select a package only because its internal source or build process\nchanged. Select it when users of that package will observe the change.\n\nEvery new icon adds a public export to all four npm packages, so select `minor`\nfor all four. `@primer/octicons-react-symbols` keeps an independent `0.x`\nversion and sits outside the linked release group, so select it explicitly.\nDo not add it to the linked group while it has an independent version line:\nChangesets versions linked releases from the highest current version in the\ngroup.\n\nThe Changesets workspace graph adds `octicons_gem`, `octicons_helper`, and\n`jekyll-octicons` to a shared icon-data release. Confirm that the changeset bot\nlists them, but do not select them solely because shared icon data changed.\nSelect a Ruby workspace directly when the pull request makes a Ruby-specific\npublic change.\n\n## Choose the version impact\n\n- `patch`: A backwards-compatible fix to existing public behavior or icon\n  output\n- `minor`: A backwards-compatible public API addition, such as a new icon or\n  export, or a canonical rename that preserves the old name as a compatibility\n  alias\n- `major`: A breaking public API change, such as removing or renaming an icon\n  or export without backwards compatibility\n\nChoose the impact independently for each affected package.\n\n## Author a changeset\n\nRun `npx changeset` and follow the prompts to select every affected package,\nchoose its version impact, and enter the description. Commit the generated\nmarkdown file in `.changeset/` to the pull request branch.\n\nUse one changeset for one user-facing change. Do not add a second changeset for\ngenerated files, snapshots, or a follow-up that only completes the same public\nAPI change.\n\nTo create one manually, add a uniquely named markdown file in `.changeset/`\nwith YAML frontmatter for all affected packages:\n\n```markdown\n---\n'@primer/octicons': minor\n'@primer/octicons-react': minor\n'@primer/octicons-react-symbols': minor\n'@primer/styled-octicons': minor\n---\n\nAdd the accessibility icon for representing accessible experiences.\n```\n\n## Write for package users\n\nThe description is published in package changelogs and release notes. Write it\nas communication to users of the library:\n\n- Describe the public API change and its user-visible effect\n- Use one or two concise sentences\n- Name relevant icons, exports, or packages when that helps users understand\n  the impact\n- Use present tense and active voice\n- Exclude implementation details, internal file names, test changes, and pull\n  request process\n\nGood:\n\n```markdown\nAdd the `AccessibilityInsetIcon` export for representing accessible\nexperiences.\n```\n\nAvoid:\n\n```markdown\nUpdate the build script and generated files after adding a new SVG, including\nsnapshot changes.\n```\n\nThe avoided example explains the implementation rather than the public API\nchange that users need to know about.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/primer/octicons/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# AGENTS.md\n\n## Running tasks\n\n- Prefer running repository tasks through Turborepo from the repository root, for example `npx turbo run build`.\n- When targeting a specific workspace, use `--filter` with its package name, for example `npx turbo run build --filter=@primer/octicons-react`.\n\n## Adding and reviewing octicons\n\n- Follow the [add-octicon checklist](docs/add-octicon-checklist.md) when adding or reviewing octicons.\n- When reviewing a pull request that adds, updates, or renames an Octicon, load and follow `.github/skills/icon-request-review/SKILL.md`. Use its contribution review phase and load only the references that phase requires.\n- Treat a pull request as an Octicon contribution when its stated purpose or diff includes icon source files, icon naming or compatibility metadata, icon keywords, or generated icon exports and snapshots. Do not load the skill for an unrelated change merely because it touches shared build or release infrastructure.\n","isInternal":false,"tokens":202,"sizeBytes":965},{"name":"SKILL.md","path":".github/skills/changesets/SKILL.md","rawUrl":"https://raw.githubusercontent.com/primer/octicons/HEAD/.github/skills/changesets/SKILL.md","title":"changesets","category":"anthropic-skill","format":"markdown","content":"---\nname: changesets\ndescription: \"Use when a pull request changes a package's public API. Covers affected packages, semantic version impact, file format, and user-focused release notes.\"\n---\n\n# Changesets\n\nThis repository uses [Changesets](https://github.com/changesets/changesets) to\nversion packages and generate changelogs. Add a changeset whenever a pull\nrequest changes the public API of a published package.\n\nA changeset records:\n\n1. Every published package affected by the public API change\n2. The semantic version impact (`patch`, `minor`, or `major`) for each package\n3. A concise description of the change for users of the affected packages\n\n## When a changeset is required\n\nAdd a changeset for consumer-facing changes such as:\n\n- Adding, removing, or renaming an icon\n- Changing an icon's rendered appearance or behavior\n- Adding, removing, or changing an export\n- Changing public JavaScript, React, CSS, or TypeScript APIs\n- Fixing behavior that users experience through a package's public API\n\nChanges that do not affect a published package's public API, such as\ndocumentation, tests, internal refactors, or CI configuration, do not need a\nchangeset. Add the `skip changeset` label to those pull requests.\n\n## Identify affected packages\n\nReview the change from the perspective of users of each package. For a new\nicon, select all npm packages whose generated public APIs change:\n\n- `@primer/octicons`\n- `@primer/octicons-react`\n- `@primer/octicons-react-symbols`\n- `@primer/styled-octicons`\n\nDo not select a package only because its internal source or build process\nchanged. Select it when users of that package will observe the change.\n\nEvery new icon adds a public export to all four npm packages, so select `minor`\nfor all four. `@primer/octicons-react-symbols` keeps an independent `0.x`\nversion and sits outside the linked release group, so select it explicitly.\nDo not add it to the linked group while it has an independent version line:\nChangesets versions linked releases from the highest current version in the\ngroup.\n\nThe Changesets workspace graph adds `octicons_gem`, `octicons_helper`, and\n`jekyll-octicons` to a shared icon-data release. Confirm that the changeset bot\nlists them, but do not select them solely because shared icon data changed.\nSelect a Ruby workspace directly when the pull request makes a Ruby-specific\npublic change.\n\n## Choose the version impact\n\n- `patch`: A backwards-compatible fix to existing public behavior or icon\n  output\n- `minor`: A backwards-compatible public API addition, such as a new icon or\n  export, or a canonical rename that preserves the old name as a compatibility\n  alias\n- `major`: A breaking public API change, such as removing or renaming an icon\n  or export without backwards compatibility\n\nChoose the impact independently for each affected package.\n\n## Author a changeset\n\nRun `npx changeset` and follow the prompts to select every affected package,\nchoose its version impact, and enter the description. Commit the generated\nmarkdown file in `.changeset/` to the pull request branch.\n\nUse one changeset for one user-facing change. Do not add a second changeset for\ngenerated files, snapshots, or a follow-up that only completes the same public\nAPI change.\n\nTo create one manually, add a uniquely named markdown file in `.changeset/`\nwith YAML frontmatter for all affected packages:\n\n```markdown\n---\n'@primer/octicons': minor\n'@primer/octicons-react': minor\n'@primer/octicons-react-symbols': minor\n'@primer/styled-octicons': minor\n---\n\nAdd the accessibility icon for representing accessible experiences.\n```\n\n## Write for package users\n\nThe description is published in package changelogs and release notes. Write it\nas communication to users of the library:\n\n- Describe the public API change and its user-visible effect\n- Use one or two concise sentences\n- Name relevant icons, exports, or packages when that helps users understand\n  the impact\n- Use present tense and active voice\n- Exclude implementation details, internal file names, test changes, and pull\n  request process\n\nGood:\n\n```markdown\nAdd the `AccessibilityInsetIcon` export for representing accessible\nexperiences.\n```\n\nAvoid:\n\n```markdown\nUpdate the build script and generated files after adding a new SVG, including\nsnapshot changes.\n```\n\nThe avoided example explains the implementation rather than the public API\nchange that users need to know about.\n","frontmatter":{"name":"changesets","description":"Use when a pull request changes a package's public API. Covers affected packages, semantic version impact, file format, and user-focused release notes."},"isInternal":false,"tokens":943,"sizeBytes":4393}],"systemPromptSnippet":"<yakaai_skills repo=\"primer/octicons\">\n<!-- File: AGENTS.md (Tokens: ~202 | Category: root-instruction) -->\n# AGENTS.md\n\n## Running tasks\n\n- Prefer running repository tasks through Turborepo from the repository root, for example `npx turbo run build`.\n- When targeting a specific workspace, use `--filter` with its package name, for example `npx turbo run build --filter=@primer/octicons-react`.\n\n## Adding and reviewing octicons\n\n- Follow the [add-octicon checklist](docs/add-octicon-checklist.md) when adding or reviewing octicons.\n- When reviewing a pull request that adds, updates, or renames an Octicon, load and follow `.github/skills/icon-request-review/SKILL.md`. Use its contribution review phase and load only the references that phase requires.\n- Treat a pull request as an Octicon contribution when its stated purpose or diff includes icon source files, icon naming or compatibility metadata, icon keywords, or generated icon exports and snapshots. Do not load the skill for an unrelated change merely because it touches shared build or release infrastructure.\n\n<!-- File: .github/skills/changesets/SKILL.md (Tokens: ~943 | Category: anthropic-skill) -->\n---\nname: changesets\ndescription: \"Use when a pull request changes a package's public API. Covers affected packages, semantic version impact, file format, and user-focused release notes.\"\n---\n\n# Changesets\n\nThis repository uses [Changesets](https://github.com/changesets/changesets) to\nversion packages and generate changelogs. Add a changeset whenever a pull\nrequest changes the public API of a published package.\n\nA changeset records:\n\n1. Every published package affected by the public API change\n2. The semantic version impact (`patch`, `minor`, or `major`) for each package\n3. A concise description of the change for users of the affected packages\n\n## When a changeset is required\n\nAdd a changeset for consumer-facing changes such as:\n\n- Adding, removing, or renaming an icon\n- Changing an icon's rendered appearance or behavior\n- Adding, removing, or changing an export\n- Changing public JavaScript, React, CSS, or TypeScript APIs\n- Fixing behavior that users experience through a package's public API\n\nChanges that do not affect a published package's public API, such as\ndocumentation, tests, internal refactors, or CI configuration, do not need a\nchangeset. Add the `skip changeset` label to those pull requests.\n\n## Identify affected packages\n\nReview the change from the perspective of users of each package. For a new\nicon, select all npm packages whose generated public APIs change:\n\n- `@primer/octicons`\n- `@primer/octicons-react`\n- `@primer/octicons-react-symbols`\n- `@primer/styled-octicons`\n\nDo not select a package only because its internal source or build process\nchanged. Select it when users of that package will observe the change.\n\nEvery new icon adds a public export to all four npm packages, so select `minor`\nfor all four. `@primer/octicons-react-symbols` keeps an independent `0.x`\nversion and sits outside the linked release group, so select it explicitly.\nDo not add it to the linked group while it has an independent version line:\nChangesets versions linked releases from the highest current version in the\ngroup.\n\nThe Changesets workspace graph adds `octicons_gem`, `octicons_helper`, and\n`jekyll-octicons` to a shared icon-data release. Confirm that the changeset bot\nlists them, but do not select them solely because shared icon data changed.\nSelect a Ruby workspace directly when the pull request makes a Ruby-specific\npublic change.\n\n## Choose the version impact\n\n- `patch`: A backwards-compatible fix to existing public behavior or icon\n  output\n- `minor`: A backwards-compatible public API addition, such as a new icon or\n  export, or a canonical rename that preserves the old name as a compatibility\n  alias\n- `major`: A breaking public API change, such as removing or renaming an icon\n  or export without backwards compatibility\n\nChoose the impact independently for each affected package.\n\n## Author a changeset\n\nRun `npx changeset` and follow the prompts to select every affected package,\nchoose its version impact, and enter the description. Commit the generated\nmarkdown file in `.changeset/` to the pull request branch.\n\nUse one changeset for one user-facing change. Do not add a second changeset for\ngenerated files, snapshots, or a follow-up that only completes the same public\nAPI change.\n\nTo create one manually, add a uniquely named markdown file in `.changeset/`\nwith YAML frontmatter for all affected packages:\n\n```markdown\n---\n'@primer/octicons': minor\n'@primer/octicons-react': minor\n'@primer/octicons-react-symbols': minor\n'@primer/styled-octicons': minor\n---\n\nAdd the accessibility icon for representing accessible experiences.\n```\n\n## Write for package users\n\nThe description is published in package changelogs and release notes. Write it\nas communication to users of the library:\n\n- Describe the public API change and its user-visible effect\n- Use one or two concise sentences\n- Name relevant icons, exports, or packages when that helps users understand\n  the impact\n- Use present tense and active voice\n- Exclude implementation details, internal file names, test changes, and pull\n  request process\n\nGood:\n\n```markdown\nAdd the `AccessibilityInsetIcon` export for representing accessible\nexperiences.\n```\n\nAvoid:\n\n```markdown\nUpdate the build script and generated files after adding a new SVG, including\nsnapshot changes.\n```\n\nThe avoided example explains the implementation rather than the public API\nchange that users need to know about.\n</yakaai_skills>"}