Skip to content
cccskills
FreePublished on GitHub

biome

Enforce Biome formatting and lint discipline in this repository. Use when making any file edits, when asked to run format/lint, and immediately before any commit. Always execute `bun run lint` (from package.json), apply resulting fixes, and re-run until clean. Treat `bun run lint:links` as optional by default, and recommend it when files under `content/` are changed.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.6 KB
  • agents/openai.yaml282 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Biome

Required Policy

Apply this policy on every task in this repository:

  1. Run bun run lint after making any file change.
  2. Run bun run lint again immediately before any git commit.
  3. Treat lint failures as blocking. Do not proceed to final delivery or commit until lint passes.

Workflow

  1. Make the requested code or content edits.
  2. Execute:
bun run lint
  1. If lint reports issues or rewrites files, review changed files and run bun run lint again until it exits cleanly.
  2. If a commit is requested, run bun run lint one final time right before git commit.
  3. Record lint execution in the task evidence/summary.

Optional Link Check Policy

  • Default: do not run bun run lint:links.
  • If the change includes files under content/, recommend running bun run lint:links.
  • If the user explicitly asks for full check, run bun run check.

Guardrails

  • Use bun run lint as the source of truth command (defined in package.json as biome check --write).
  • Do not replace this with direct biome CLI variants unless user explicitly asks for a different command.
  • Keep bun run lint:links optional unless content/ changed or the user explicitly requests it.
  • Keep lint-induced edits in scope; avoid unrelated refactors.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Execute a frozen workflow contract and collect evidence by implementing only approved scope/files and checks. Use when PLAN_FROZEN=true and Execution Contract is complete, then hand off to review.

The English summary is being prepared. Showing the original description.

TEN-framework/portal42Updated May 9, 2026

Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.

The English summary is being prepared. Showing the original description.

TEN-framework/portal42Updated May 9, 2026

Review execution against the frozen Execution Contract, produce Evidence/Gaps, and decide pass or unfreeze. Use after ac-execute or at milestone acceptance gates.

The English summary is being prepared. Showing the original description.

TEN-framework/portal42Updated May 9, 2026

See all skills by TEN-framework

Report a problem with this skill