@timmo001/oxlint-rules 0.2.0 → 0.3.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timmo001/oxlint-rules",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Shared Oxlint plugins and configs with optional Effect rules.",
   "type": "module",
   "license": "Apache-2.0",
@@ -17,7 +17,7 @@
     "./generic": "./dist/generic/index.js",
     "./effect": "./dist/effect/index.js",
     "./configs/recommended": "./dist/configs/recommended.js",
-    "./configs/effect": "./dist/configs/effect.js"
+    "./configs/recommended-effect": "./dist/configs/recommended-effect.js"
   },
   "files": [
     "dist",
@@ -40,7 +40,7 @@
     "format": "prettier --write \"{src,scripts}/**/*.ts\" \"skills/**/*.{md,mjs}\" \"*.md\" \"*.json\"",
     "format:check": "prettier --check \"{src,scripts}/**/*.ts\" \"skills/**/*.{md,mjs}\" \"*.md\" \"*.json\"",
     "lint": "oxlint src scripts",
-    "skills:validate": "bunx skills-ref validate skills/install-timmo-oxlint-rules && bunx skills-ref validate skills/add-oxlint-rule",
+    "skills:validate": "bunx skills-ref validate skills/install-timmo-oxlint-rules && bunx skills-ref validate skills/add-oxlint-rule && bunx skills-ref validate skills/release-oxlint-rules",
     "test": "node --experimental-strip-types scripts/test.ts",
     "typecheck": "tsc --noEmit"
   },

package/skills/add-oxlint-rule/SKILL.md

@@ -26,7 +26,10 @@ description: >-
    and behaviour description. Keep skills workflow-only; do not duplicate rule
    or plugin inventories or counts in them.
 7. Run `mise run check`, `mise run build`, `npm pack --dry-run`, and
-   `bunx jsr@0.14.3 publish --dry-run` in the central checkout.
+   `bunx jsr@0.14.3 publish --dry-run --allow-dirty` in the central checkout.
+8. If the user also asks to publish the change, load `release-oxlint-rules` and
+   hand off the release after the rule checks pass. Do not duplicate or bypass
+   its release workflow.
 
 Report the fixture contract, registration and docs changed, checks, and any
 consumer rollout left for a separate stage. Do not publish or assume a local

package/skills/install-timmo-oxlint-rules/SKILL.md

@@ -24,8 +24,9 @@ description: >-
    and lockfile. Add an exact development dependency through that package
    manager.
 3. Extend `@timmo001/oxlint-rules/configs/recommended`. The config owns plugin
-   registration and recommended severities. Use `/configs/effect` instead only
-   when `effect` is a direct dependency or the user explicitly requests it.
+   registration and recommended severities. Use `/configs/recommended-effect`
+   instead only when `effect` is a direct dependency or the user explicitly
+   requests it.
 4. Keep dependency and config edits visible. Do not delegate them to a script.
 
 ## Copy rules

package/skills/release-oxlint-rules/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: release-oxlint-rules
+description: >-
+  Create and publish a major, minor, or patch release of
+  @timmo001/oxlint-rules. Use when asked to create, cut, prepare, or publish an
+  oxlint-rules release, including its version bump and npm and JSR publication.
+---
+
+# Release Oxlint Rules
+
+1. Find a writable checkout whose Git remote is
+   `timmo001/oxlint-rules`. Read its `AGENTS.md`, package metadata, release
+   workflow, latest tags, and changes since the latest release. Stop if the
+   worktree contains unrelated changes or the local branch is behind its
+   remote.
+2. Confirm `package.json` and `jsr.json` have the same current version and that
+   its release exists. Resolve the next version from the requested major,
+   minor, patch, or exact version. Ask only when the release level is missing.
+   Do not add a `v` prefix when the repository's existing tags omit it.
+3. Update the version in `package.json` and `jsr.json`. Before committing, run
+   `mise run check`, `mise run build`, `npm pack --dry-run`, and
+   `bunx jsr@0.14.3 publish --dry-run --allow-dirty`. The dirty-tree flag is
+   required because the intended version bump is not committed yet.
+4. Treat a direct request to create or publish the release as authorisation for
+   its version commit, push, and GitHub release. Follow the active environment's
+   guarded commit and push workflow, committing only the release metadata with
+   `Release Oxlint rules <version>`. A request to prepare or plan a release does
+   not authorise publication.
+5. Resolve the target only after the push with `git rev-parse HEAD`. Pass the
+   resulting full 40-character SHA as the `--target` value when running
+   `gh release create`. Never pass an abbreviated SHA as `target_commitish`.
+6. Create the release before resolving workflow targets because publication is
+   triggered by the `release.published` event. Watch only the release commit's
+   exact workflow runs and require both `Publish to npm` and `Publish to JSR` to
+   succeed.
+7. Report the release URL, version commit, validation results, and npm and JSR
+   publication conclusions. Do not report the release as complete while either
+   publication job is pending or failed.