Index of every page on this site: llms.txt
All skills
corey-alix avatar

/package-json-commenter

@e4fbc1d
Run it yourself

Ensures any new or modified package.json script commands include a paired comment entry describing the command.

Use this Skill: https://skilld.dev/gh/corey-alix/dwp-hours/package-json-commenter

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈34 tokens for metadata: the name and description. ≈272 when used: this file.

Description uses 1.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈136 characters, or 1.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Package.json Command Commenter

Description

Ensures any new or modified package.json script commands include a paired // comment entry describing the command.

Trigger

Activate when the user asks to add, change, or generate package.json scripts, or when creating new npm commands in any context.

Response Pattern

  1. Identify each package.json script command being added or modified.
  2. Add a matching "<scriptName>//" comment entry with a concise description for every command created.
  3. Keep comments near their associated command and preserve existing ordering/style.
  4. Validate that every new command has a corresponding comment entry before finishing.

Examples

  • "Add a new npm script to run lint fixes"
  • "Create a build:assets script in package.json"
  • "Update the start script to use nodemon"

Additional Context

  • Use the project convention: pair each script with a // comment key (e.g., start//).
  • Keep descriptions short and action-oriented.
  • When relevant, reference TASKS priorities and ensure scripts align with project standards.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts5mo3 checks · Risk SAFE
  • Gen Agent Trust Hub5mo

    This skill is safe. It assists users in documenting npm scripts within package.json files by automatically adding paired comment entries.

  • Socket5mo

    No alerts

  • Snyk5mo

    Risk: LOW · No issues

Signed by skilld at e4fbc1d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago

README badge

README badge for corey-alix/dwp-hours/package-json-commenter