init

Launches a terminal UI wizard that helps you create pixelartlint.toml with an inlined palette section ready for version control and CI.

Terminal
pixel-art-lint init

Wizard flow

  1. Pick a palette source: an Aseprite file (.aseprite) a reference image (PNG/BMP/JPG) or a Lospec palette.
  2. Select the source file from matches under the current working directory.
  3. Choose which folder should receive the generated config.
  4. Preview the TOML, confirm overwrite if a config already exists, then write the file.

Aseprite source

The wizard searches for **/*.aseprite under the repo. It reads the embedded palette from the file you pick and writes those colours into [tool.pixel_linter.palette]. Choose a sprite whose palette matches what you lint in CI—often a master sheet or a dedicated palette file your team already commits.

Reference image source

When you pick a reference image, colours are collected from pixels in that file and written into the [tool.pixel_linter.palette] section as hex values.

Lospec source

Uses the Lospec API to download the json file matching the palette slug. If the palette is not found, an error is shown to the user to correct the slug.

After init

Run a first lint pass from the same tree:

Terminal
pixel-art-lint check

Adjust severities and rules in configuration as your pipeline matures.