upgrade-simple-icons_skill

This skill upgrades simple-icons to the latest version while preserving removed icons by sourcing them into customIcons.ts and updating mappings.
  • TypeScript

2.2k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill wei/socialify --skill upgrade-simple-icons

  • SKILL.md1.4 KB

Overview

This skill upgrades the simple-icons dependency to the latest version while preserving any icons removed or renamed by the update. It automates the process of sourcing missing icon data from the prior package and consolidating those entries into a custom icons module. The goal is a smooth version bump with no visual regressions in icon mappings.

How this skill works

First, record the current simple-icons version and install simple-icons@latest. The skill scans language mapping imports and runs lint/verify to detect missing icon exports. For any missing icons, it extracts the icon data from the recorded previous version, creates a custom icon entry in common/icons/customIcons.ts, updates mappings to use the custom entry, and fixes import ordering. Finally, it verifies the project and generates a changeset for the upgrade.

When to use it

  • Before merging a dependency bump that updates simple-icons.
  • When lint or build reports missing simple-icons exports after an upgrade.
  • When icons in the UI appear broken or missing after a package update.
  • When preparing a release that includes a dependency version change.

Best practices

  • Record the exact previous simple-icons version from package.json and pnpm-lock.yaml before upgrading.
  • Run pnpm lint and pnpm verify immediately after installing the new package to surface missing exports.
  • Extract full icon data (title, slug, hex, path) from the previous package rather than hand-crafting values.
  • Add custom icons to common/icons/customIcons.ts and update languageMapping.ts to reference them—keep naming consistent (custom<IconName>).
  • Run pnpm lint:fix to correct import ordering, then remove temporary files or installed snapshots.
  • Add a changeset and update docs for any mapping or behavior changes before committing.

Example use cases

  • Bumping simple-icons as part of routine dependency maintenance while ensuring no removed icons break pages.
  • Recovering a brand icon that was dropped in the latest simple-icons release by sourcing it from the previous version.
  • Preparing a deploy where CI fails due to missing icon exports and quickly patching mappings with custom icons.
  • Contributing a patch that upgrades simple-icons during Hacktoberfest while preserving project visuals.

FAQ

No. Install or download the previous version only long enough to extract icon JSON; remove it afterward to keep dependencies clean.

What fields must I include for a custom icon entry?

Include title, slug, hex, and path from the original icon data so the icon renders and maps identically.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational