You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: address review findings for the checks feature
- Merge the tool-scoped 'amp:' frontmatter section with precedence over
canonical values (per feature-change-guidelines), exclude all
tool-target sections from the passthrough so they no longer leak into
generated check files, and keep 'name' pinned to the file basename.
- Reuse AMP_GLOBAL_DIR for AMP_CHECKS_GLOBAL_DIR.
- Add checksCount to the result-shape assertions in the MCP tests and
add checks feature suites to lib/import and lib/convert tests.
- Update the DIR_FEATURES comment to mention checks.
- Document the tool-scoped section behavior for checks.
The reviewer's note about 'does not support the feature checks' warning
noise for wildcard features is intentionally unchanged: it is the
established warnUnsupportedTargets pattern shared by every feature core,
and changing warning policy is a cross-feature UX decision out of scope
here.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/reference/file-formats.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -448,7 +448,7 @@ The emitted Amp frontmatter is derived from the source as follows:
448
448
|`severity-default`|`severity`|
449
449
|`tools`|`tools`|
450
450
451
-
The frontmatter schema is loose, so any extra Amp-specific keys survive a generate/import round-trip. On import, `severity-default` maps back to the generic `severity` field, and the `name` field is dropped because it is re-derived from the file name on the next generate.
451
+
The frontmatter schema is loose, so any extra Amp-specific keys survive a generate/import round-trip. A tool-scoped section (e.g. `amp: { "severity-default": "critical" }`) overrides the canonical values for that tool — the tool-specific value takes precedence, and the section itself is not emitted (except `name`, which always comes from the file name). On import, `severity-default` maps back to the generic `severity` field, and the `name` field is dropped because it is re-derived from the file name on the next generate.
452
452
453
453
> **v1 limitation:** Amp also discovers subtree-scoped checks (e.g. `api/.agents/checks/`), but rulesync sources carry no directory-placement semantics, so those subtree-scoped checks are not generated. See the [Amp manual](https://ampcode.com/manual).
Copy file name to clipboardExpand all lines: skills/rulesync/file-formats.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -448,7 +448,7 @@ The emitted Amp frontmatter is derived from the source as follows:
448
448
|`severity-default`|`severity`|
449
449
|`tools`|`tools`|
450
450
451
-
The frontmatter schema is loose, so any extra Amp-specific keys survive a generate/import round-trip. On import, `severity-default` maps back to the generic `severity` field, and the `name` field is dropped because it is re-derived from the file name on the next generate.
451
+
The frontmatter schema is loose, so any extra Amp-specific keys survive a generate/import round-trip. A tool-scoped section (e.g. `amp: { "severity-default": "critical" }`) overrides the canonical values for that tool — the tool-specific value takes precedence, and the section itself is not emitted (except `name`, which always comes from the file name). On import, `severity-default` maps back to the generic `severity` field, and the `name` field is dropped because it is re-derived from the file name on the next generate.
452
452
453
453
> **v1 limitation:** Amp also discovers subtree-scoped checks (e.g. `api/.agents/checks/`), but rulesync sources carry no directory-placement semantics, so those subtree-scoped checks are not generated. See the [Amp manual](https://ampcode.com/manual).
0 commit comments