Skip to content

Align skill and validator with StructKit 3.3.0 .structkit.yaml - #3

Merged
httpdss merged 1 commit into
mainfrom
cursor/structkit-yaml-rename-e298
Oct 8, 2026
Merged

httpdss merged 1 commit into
mainfrom
cursor/structkit-yaml-rename-e298

Conversation

@httpdss

@httpdss httpdss commented Oct 8, 2026

Copy link
Copy Markdown
Owner

StructKit v3.3.0 renamed the default project file from .struct.yaml to .structkit.yaml. This updates the skill, references, and repo validator to match, while keeping legacy names working.

Flag names were checked against httpdss/structkit on main (structkit/commands/generate.py, docs/hooks.md, docs/cli-reference.md).

Validator

scripts/validate_structkit_repo.py now finds:

  • .structkit.yaml / .structkit.yml
  • *.structkit.yaml / *.structkit.yml
  • legacy .struct.yaml / .struct.yml and *.struct.yaml / *.struct.yml

Discovery walks the tree and matches those suffixes so hidden project files are found on Python 3.11 (CI Path.glob('**/*.struct.yaml') skips names that start with .).

New tests cover canonical, named, and legacy files. CI runs unittest before the existing validate step.

Skill and docs

  • Default examples and checklists use .structkit.yaml.
  • One-line note that structkit generate still reads legacy .struct.yaml.
  • Brief 3.3.0 guidance: hook safety (--no-hooks, STRUCTKIT_NO_HOOKS, .struct-hooks-allowlist, MCP no_hooks) and structkit config print.
  • Skill version 0.1.0 → 0.2.0.

Template files in templates/*.struct.yaml are unchanged; they remain valid named structures.

Open in Web Open in Cursor 

Discover canonical .structkit.yaml files (and *.structkit.yaml) in repo
validation while still accepting legacy .struct.yaml names. Document the
default project file, hook safety flags, and structkit config print.

Co-authored-by: Kenneth Belitzky <kenny@belitzky.com>
@httpdss
httpdss marked this pull request as ready for review October 8, 2026 10:03
@httpdss
httpdss merged commit d144169 into main Oct 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants