@doki-land/nifty-skills 0.0.6 → 0.0.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@doki-land/nifty-skills",
3
- "version": "0.0.6",
3
+ "version": "0.0.8",
4
4
  "description": "Agent Skills for Nifty gitmoji commits, npm release, and git history tooling",
5
5
  "type": "module",
6
6
  "license": "MPL-2.0",
@@ -24,8 +24,8 @@
24
24
  "typecheck": "node -e \"console.log('docs-only skill package')\""
25
25
  },
26
26
  "optionalDependencies": {
27
- "@doki-land/nifty-win32-x64": "0.0.6",
28
- "@doki-land/nifty-linux-x64": "0.0.6",
29
- "@doki-land/nifty-darwin-arm64": "0.0.6"
27
+ "@doki-land/nifty-win32-x64": "0.0.8",
28
+ "@doki-land/nifty-linux-x64": "0.0.8",
29
+ "@doki-land/nifty-darwin-arm64": "0.0.8"
30
30
  }
31
31
  }
@@ -14,7 +14,7 @@ workspaces. Native git work uses **gix** (Rust). Changelog tag ranges use the `g
14
14
  ## Before you act
15
15
 
16
16
  1. Confirm `@doki-land/nifty` is installed (`nifty --help`) or use `pnpm exec nifty` in the npm-tools repo.
17
- 2. Look for `nifty.config.ts` at the project root (`defineConfig`, `authorMap`, `publish.packages`, `changelog.*`).
17
+ 2. Look for `nifty.config.ts` at the project root (`defineConfig`, `authorMap` path to `author-github.json`, `publish.packages`, `changelog.*`).
18
18
  3. Load a focused sub-skill when the task is narrow (see table below).
19
19
 
20
20
  ## Sub-skills
@@ -31,6 +31,11 @@ nifty check --from origin/dev..HEAD
31
31
  # Commit-only scan/audit (gitmoji + semver/semicolon/backtick hygiene)
32
32
  nifty commit scan --from d25daeba^ --to HEAD
33
33
  nifty commit audit --from d25daeba^ --to HEAD
34
+ nifty commit audit --from d25daeba^ --to HEAD --errors-only
35
+ nifty commit audit --from d25daeba^ --to HEAD --json
36
+
37
+ # Export a reword map and annotate violations in-place
38
+ nifty commit export --base d25daeba --ref dev --path commit.pending.json --with-lint
34
39
 
35
40
  # Lint explicit strings
36
41
  nifty lint --subject "✨ Add feature"
@@ -62,9 +67,13 @@ Align with Nifty/npm-tools git policy when the user asks you to commit:
62
67
 
63
68
  ## Workflow
64
69
 
65
- 1. Run `nifty commit scan` on the range about to merge or release.
66
- 2. Fix subjects locally or plan a **`nifty commit export` / `nifty commit apply`** pass (see `nifty-git-history`) for
67
- history already pushed.
68
- 3. Re-run `nifty commit audit` until exit code is 0.
70
+ 1. Run `nifty commit audit` on the range about to merge or release.
71
+ 2. For history rewrites, export with lint annotations:
72
+ `nifty commit export --base <exclusive-base> --ref dev --path commit.pending.json --with-lint`
73
+ 3. Edit only entries with `violations` (or all subjects that need changes), then apply with `nifty commit apply`.
74
+ 4. Re-run `nifty commit audit` until exit code is 0.
75
+
76
+ `scan` and `audit` group findings by commit hash, print a per-rule summary, and support `--json` for automation.
77
+ `export --with-lint` writes the same `violations` array onto each JSON entry. `commit apply` ignores that field.
69
78
 
70
- Do not bypass lint with custom regex when `nifty commit scan` is available.
79
+ Do not bypass lint with custom regex or one-off scripts when `nifty commit audit` is available.
@@ -17,16 +17,16 @@ Warn the user before rewriting shared branches. Prefer `--dry-run` first.
17
17
  Export JSON map, preview, apply:
18
18
 
19
19
  ```bash
20
- nifty commit export --base 34e1e665^ --ref dev --path commit.pending.json
21
- nifty commit apply --base 34e1e665^ --ref dev --path commit.pending.json --dry-run
22
- nifty commit apply --base 34e1e665^ --ref dev --path commit.pending.json
20
+ nifty commit export --base 34e1e665 --ref dev --path commit.pending.json --with-lint
21
+ nifty commit apply --base 34e1e665 --ref dev --path commit.pending.json --dry-run
22
+ nifty commit apply --base 34e1e665 --ref dev --path commit.pending.json
23
23
  ```
24
24
 
25
- Scan or audit the same commit range before editing:
25
+ Audit the same commit range before or after editing:
26
26
 
27
27
  ```bash
28
- nifty commit scan --from 34e1e665^ --to dev
29
- nifty commit audit --from 34e1e665^ --to dev
28
+ nifty commit audit --from 34e1e665 --to dev
29
+ nifty commit audit --from 34e1e665 --to dev --errors-only
30
30
  ```
31
31
 
32
32
  ### Map format
@@ -14,9 +14,8 @@ Create or extend `nifty.config.ts`:
14
14
  ```ts
15
15
  export default {
16
16
  githubToken: process.env.GITHUB_TOKEN,
17
- authorMap: { "you@example.com": { login: "handle", id: 12345 } },
17
+ authorMap: "documentation/maintenance/author-github.json",
18
18
  changelog: {
19
- authorMap: "documentation/maintenance/author-github.json",
20
19
  releasesDir: "documentation/maintenance/releases",
21
20
  repo: "owner/name",
22
21
  },