Index of every page on this site: llms.txt
All skills
chelis-lang avatar

/spec-sync

@f7af876
Run it yourself

Use when changing Chelis language behavior, CLI behavior, or compiler semantics. Keeps code, tests, examples, and active specs in sync in one change set.

  • 1 file
  • 1.3 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/chelis-lang/chelis/spec-sync

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈41 tokens for metadata: the name and description. ≈280 when used: this file.

Description uses 2.1% 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 ≈165 characters, or 2.1%.

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.

Spec Sync

Use this skill whenever a change affects public language/compiler behavior.

Required Sync Surfaces

  • owning implementation files
  • unit/integration/e2e tests
  • executable examples in examples/
  • active specs in spec/
  • current-state docs such as README.md and the canonical reference when needed

Repository Rules

  • Prefer updating the owning active doc over adding new explanation docs.
  • Do not treat spec/design/archive/ as current guidance.
  • If the change invalidates an example, either rewrite it to remain executable or move it to examples/illustrative/.
  • If the change affects a completion claim, update the phase oracle docs and any current phase-status summary in the same change set.

Verification

Run the pre-push gate after the edits, then require applicable CI checks to pass on the pushed candidate before ready-for-review:

python3 scripts/gate.py --fast

python3 scripts/gate.py --validation is optional for troubleshooting or additional local validation. It is not a per-PR requirement and does not replace a named acceptance oracle or manual gate.

Source: SKILL.md on GitHub

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 third-party reports yet.

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

Last checked against GitHub last week.

Activeupdated 2 months ago

README badge

README badge for chelis-lang/chelis/spec-sync