taste lint

Validate taste file format and structure. This command checks your taste files for errors and warnings before pushing.

Usage

Basic usage

npx taste lint <package>

Arguments

Argument	Description
`[package]`	Package name to lint. Optional if using `--all`.

Options

Option	Short	Description
`--global`	`-g`	Lint packages from global (`~/.commandcode/taste`)
`--all`		Lint all packages

Examples

Lint a specific package

Lint single package

npx taste lint cli

Validates the cli taste package in your local project.

Lint all local packages

Lint all local

npx taste lint --all

Validates all taste packages in your local project's .commandcode/taste directory.

Lint from global

Lint global

npx taste lint cli -g

Validates the cli package from your global.

Lint all from global

Lint all global

npx taste lint --all -g

Validates all packages in your global at ~/.commandcode/taste.

Output

The command provides detailed validation results:

Example output (valid)

taste.md
✓ File is valid

cli/taste.md
✓ File is valid

Summary: 0 errors, 0 warnings across 2 files
✓ All 2 taste files are valid

Example output (with errors)

cli/taste.md
✗ 2 errors found

  Line 5: Invalid confidence value (must be between 0 and 1)
  Line 12: Missing required header

Summary: 2 errors, 0 warnings across 1 file
✗ Validation failed

What Gets Validated

Check	Description
Markdown structure	Proper header hierarchy and formatting
Required fields	Presence of required metadata and sections
Confidence values	Values must be between 0 and 1
Header format	Correct header syntax and naming
File encoding	Valid UTF-8 encoding

Behavior

Validates both main taste.md and category-specific taste files
Supports automatic header migration for legacy format files
Errors indicate problems that must be fixed before pushing
Warnings indicate potential issues but don't block operations

Next steps

Fix any errors reported by the linter
Use taste push to upload validated packages
Use taste open to edit packages with errors

Reference