Overview - Intent

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
feat/validate-code-blocks
21188f2c test: initialize the prose fixture before each benchmark run
by ladybluenotes
Succeeded
feat/validate-code-blocks
1370c735 fix: give each virtual example file the extension of its fence language
by ladybluenotes
Succeeded
feat/validate-code-blocks
f573b312 perf: group skills by library in one pass instead of re-spreading per skill
by Sarah Gerrard
Succeeded
feat/validate-code-blocks
ebe289a9 test: give every fixture commit an author so the suite passes without a global Git identity
by Sarah Gerrard
Failed
feat/validate-code-blocks
8b2e17e9 fix: key virtual example files the way TypeScript reads them and drop the deprecated baseUrl TypeScript hands the compiler host forward-slash paths, so on Windows the backslash-keyed virtual files were never found and every example passed unchecked. TypeScript 6 reports baseUrl as an error, and the path mappings are absolute, so it is removed. Syntax errors are now reported, since an example that does not parse is not checked at all, and declaration-only source entries are accepted when build output is ignored.
by Sarah Gerrard
Failed
feat/validate-code-blocks
ccccc516 ci: apply automated fixes
by autofix-ci...
Succeeded
feat/validate-code-blocks
d725193d chore: keep skill example helpers module-private for knip
by ladybluenotes
Failed
feat/validate-code-blocks
740e8af2 fix: accept angle-bracket link destinations in skill link checks CommonMark allows a link destination wrapped in <...>, which the loader already emits for shared references. The link check treated the brackets as part of the path and failed the packed-release lifecycle test.
by ladybluenotes
Failed
feat/validate-code-blocks
8512eff1 fix: address review findings on skill example checks Skip links inside fenced examples, map library subpaths to the entry directory before the package root, resolve a non-owning metadata.library through the workspace or node_modules instead of this package's entry, and require TypeScript 5.0 or newer rather than falling back to the classic resolver.
by ladybluenotes
Failed
feat/validate-code-blocks
ba9b6143 perf: typecheck each skill once per process and batch review summaries `maintainer check` validated every skill and then built a second program for each pending review item. Keep each skill's result for the process, keyed on the resolved library entry and its mtime, and describe all pending skills in one program per package.
by ladybluenotes
Failed
feat/validate-code-blocks
c9445dff fix: resolve sibling workspace packages when checking skill examples Map every workspace package to its own entry in the typecheck program. An example that imports a sibling package, such as an adapter or a framework binding, was resolving to nothing, which hid missing exports there and widened generics parameterized on those values so that wrong options and model names passed silently.
by ladybluenotes
Failed
feat/validate-code-blocks
16a9f045 fix: resolve the library entry from declared types, mapping build output to source
by ladybluenotes
Failed
feat/validate-code-blocks
ee1b329c feat: typecheck skill code blocks against the library's own source `validate` now extracts every fenced TypeScript and JavaScript block from each SKILL.md and typechecks it in one in-memory program per skills directory, with the library resolved to the owning package's source. A renamed export, a removed option, or a changed shape fails validation with the skill file and line. Names, modules, and globals a partial snippet leaves out are filtered out, so examples do not have to be complete. Imports of exports marked @deprecated produce warnings, and relative Markdown links must resolve. TypeScript is loaded from the maintainer's repository, with a fallback to Intent's own location; without it the code checks are skipped with one notice. Pending review items for skills report whether their examples still compile, so a maintainer can tell a shape change from a behavior change before opening the diff.
by ladybluenotes