Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36413
247372e6 chore(repo): fix upper-bound checklist and cover backfilled ladder rungs in author-migration skill The pre-PR checklist required "no upper bound on the entry's own gate", contradicting the section 2 rule that permits one when the migration is inapplicable at or above the cap (the next-15 instructions gate is a valid instance). The checklist item now names the source-window case as the defect and defers to section 2 for the valid exception. The packageJsonUpdates ladder rules only covered rungs shipped together in oldest-source-first key order. A rung backfilled at a later nx version sits after the existing upper rungs, so its cohort lands on the intermediate major with the upper groups permanently behind it. Document the choice between re-offering the upper rungs (with landing-gated companion entries re-stamped) and deliberately holding the cohort.
by Leosvel Pé...
Succeeded
36413
c76190a8 chore(repo): clarify template contracts and doc style in author-migration skill The migrations-json template opened with "replace the placeholders" while its JSON blocks use concrete example values and no placeholders at all; the intro now states that values are illustrative and the key sets and path shapes are the contract. alwaysAddToPackageJson appeared in both packageJsonUpdates examples unexplained, and the documentation template never said the sample-code-changes section can be omitted for changes with no code shape. Migration documentation renders on nx.dev but sits outside every docs validation: vale's scope is astro-docs/src/content only and the site synthesizes migration pages from the colocated .md files at build time without linting them (a shipped doc already fails the Nx.Headings sentence-case rule). The documentation template's own Sample Code Changes heading taught that violation; it is now sentence case, and the template and section 6 point at the docs style guide with a note that vale does not reach these files today.
by Leosvel Pé...
Canceled
36413
71f39c0f chore(repo): clarify template contracts and doc style in author-migration skill The migrations-json template opened with "replace the placeholders" while its JSON blocks use concrete example values and no placeholders at all; the intro now states that values are illustrative and the key sets and path shapes are the contract. alwaysAddToPackageJson appeared in both packageJsonUpdates examples unexplained, and the documentation template never said the sample-code-changes section can be omitted for changes with no code shape. Migration documentation renders on nx.dev but sits outside every docs validation: vale's scope is astro-docs/src/content only and the site synthesizes migration pages from the colocated .md files at build time without linting them (a shipped doc already fails the Nx.Headings sentence-case rule). The documentation template's own Sample Code Changes heading taught that violation; it is now sentence case, and the template and section 6 point at the docs style guide with a note that vale does not reach these files today.
by Leosvel Pé...
Succeeded
36413
1db4a552 chore(repo): clarify template contracts and doc style in author-migration skill The migrations-json template opened with "replace the placeholders" while its JSON blocks use concrete example values and no placeholders at all; the intro now states that values are illustrative and the key sets and path shapes are the contract. alwaysAddToPackageJson appeared in both packageJsonUpdates examples unexplained, and the documentation template never said the sample-code-changes section can be omitted for changes with no code shape. Migration documentation renders on nx.dev but sits outside every docs validation: vale's scope is astro-docs/src/content only and the site synthesizes migration pages from the colocated .md files at build time without linting them (a shipped doc already fails the Nx.Headings sentence-case rule). The documentation template's own Sample Code Changes heading taught that violation; it is now sentence case, and the template and section 6 point at the docs style guide with a note that vale does not reach these files today.
by Leosvel Pé...
Succeeded
36413
ebd5dc2d chore(repo): delegate mechanical checks to repo validators in author-migration skill The skill restated checks the repo validators enforce: path resolution, orphaned files, duplicate entry keys, the published dist shape, and packageGroup membership. Section 5 now instructs running the validators (plugin test/lint plus the conformance check) and the pre-PR checklist keeps only the judgment items no validator covers, such as whether a path names the right file, train and `requires` semantics, spec coverage, and .md claim accuracy. Target-train arithmetic moves from prose into scripts/compute-target-versions.mjs, anchored on `npm view nx dist-tags` alone; the git tag listing added nothing the dist-tags do not carry. The script prints each candidate train with the recommended default marked and guards the mid-promotion window where a stable `next` sits above `latest`. The local-registry walkthrough now includes the `npm adduser` login step from CONTRIBUTING.md, and the `nx migrate` invocations run through `npx`.
by Leosvel Pé...
Succeeded
36413
cdffd36a chore(repo): encode agentic context, spec, and docs policies in author-migration skill The runtime contract missed the agentic validation flow: generator-only migrations that produce changes get an agent validation step that receives the captured generator output and any returned agentContext, and may apply minor in-scope fixes. The skill now steers every migration with skipped or residual work to return { nextSteps, agentContext }, not just hybrids, and documents that nextSteps never reaches the agent while agentContext also surfaces on stdout when running inside an outer agent. Prompt-only entries get no spec file (nothing imports a prompt .md and no harness exercises prompt content); the spec canon, checklist, layout, and spec skeleton now say so. Every generators entry ships a documentation .md set on its documentation key, and the docs-site wording follows the key-driven rendering (nothing inferred from the implementation basename), which also retires the docs-site-leak rationale for distinct prompt filenames in favor of the documentation file owning the implementation's basename. Also corrects the overbroad claim that path validation misses any wrong dist shape (it fails shapes whose stripped path misses the source tree) and notes that prompt-runbook exemplars vary their heading names.
by Leosvel Pé...
Succeeded
36413
1164c701 chore(repo): correct and tighten author-migration skill after deep review A ten-reviewer audit of the skill (correctness against the migrate runtime, internal coherence, published skill-authoring guidance, token efficiency, steering quality) surfaced a set of verified issues: - fix three stale or wrong facts: assertValidMigrationPaths now has a file-granular orphan check (only .md files and helpers escape it), the generated migrations file carries the full entry rather than package+name, and devkit glob is deprecated in place, not deleted - close checklist and template drift: the pre-PR checklist now covers all seven mandatory spec cases, first-migration wiring, and the shipped-fix version re-stamp; the spec skeleton points at the single mandatory-case list instead of restating a subset; the prompt-only entry template gains the documentation key it was contradicting the canon by omitting - state where entries live (the generators section) in SKILL.md and the template, and show the full new-file shape - widen the treatment table's Nothing row to match the prose, add the ported-vs-source-transform tiebreaker, cover the next==latest train case, and give the between-branches classification gap a default - sharpen undecidable wording (inferred-plugin scan trigger, generator-schema check for keepExistingVersions/skipFormat, ifPackageInstalled as a live but unused runtime gate) and align terminology (packageJsonUpdates group, target train) - trim restated facts (landing-version semantics, tree-util import note, cli/schema bullet) and rephrase the rspack ungated-group citation as a historical fact so an upstream fix does not falsify it
by Leosvel Pé...
Succeeded
36413
861af83d chore(repo): refine author-migration skill gating, entry-key, and test rules Round-7 validation runs (jest, maven, nest, devkit scenarios) surfaced gaps the skill text either caused or failed to prevent: - forbid inferring a packageJsonUpdates group's requires posture from sibling groups; re-derive per admission (the ungated rspack 21.4.0 group next to its gated react twin is the counterexample) - relax the entry-key canon to a soft convention: keys stay unique and slug-bearing but follow the file's dominant form; document that JSON.parse silently drops the earlier of two duplicate keys and that a version part in the key is a release-level hint, not tied to the version field - tighten the version ask-step: a re-stamped version is still a train choice, and a run counts as non-interactive only when there is no channel to ask - add migration-homing guidance and the collection-scope contract (installed versions resolve by node resolution from the workspace root) - require materialized option values to land where the tool reads them, never as undeclared target options riding executor passthrough - add two mandatory spec rules: a drift check for frozen copies of another module's canonical set, and case-by-case coverage when a migration statically replicates deleted runtime behavior
by Leosvel Pé...
Succeeded
36413
aea40628 chore(repo): use documented migration terminology in author-migration skill The skill called the deterministic half of a migration a codemod, a term the Nx docs and the migrate source never use for it: the documented vocabulary is migration generator, with generator-only, prompt-only, and hybrid as the kinds, and codemod in the repo refers to external npx-runnable tools. Rename accordingly across SKILL.md, the templates, and the runtime contract. Codemod stays only for upstream tools (the Run upstream codemod treatment and the runbook rule), the old Codemod table row and section become Source transform (the kind names would over-claim there, since config edits and conditional dep changes are also migration generators), and one gloss binds the general-usage term to the documented one.
by Leosvel Pé...
Canceled
36413
d3b8fc94 chore(repo): use documented migration terminology in author-migration skill The skill called the deterministic half of a migration a codemod, a term the Nx docs and the migrate source never use for it: the documented vocabulary is migration generator, with generator-only, prompt-only, and hybrid as the kinds, and codemod in the repo refers to external npx-runnable tools. Rename accordingly across SKILL.md, the templates, and the runtime contract. Codemod stays only for upstream tools (the Run upstream codemod treatment and the runbook rule), the old Codemod table row and section become Source transform (the kind names would over-claim there, since config edits and conditional dep changes are also migration generators), and one gloss binds the general-usage term to the documented one.
by Leosvel Pé...
Succeeded
36413
fe6ac36d chore(repo): make author-migration skill version choice developer-driven and codemod-first
by Leosvel Pé...