@doki-land/nifty-skills 0.1.10 → 0.1.12
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
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
"description": "Agent Skills for Nifty gitmoji commits, npm release, and git history tooling",
|
|
6
6
|
"files": [
|
|
7
7
|
"skills",
|
|
8
|
-
"
|
|
8
|
+
"readme.md"
|
|
9
9
|
],
|
|
10
10
|
"homepage": "https://github.com/oovm/npm-tools/tree/dev/projects/packages/nifty-skills#readme",
|
|
11
11
|
"license": "MPL-2.0",
|
|
@@ -22,5 +22,5 @@
|
|
|
22
22
|
"typecheck": "node -e \"console.log('docs-only skill package')\""
|
|
23
23
|
},
|
|
24
24
|
"type": "module",
|
|
25
|
-
"version": "0.1.
|
|
25
|
+
"version": "0.1.12"
|
|
26
26
|
}
|
package/skills/nifty/SKILL.md
CHANGED
|
@@ -50,7 +50,7 @@ Global flag: `-C, --cwd <dir>`.
|
|
|
50
50
|
```text
|
|
51
51
|
projects/crates/ # Rust libraries + nifty-napi
|
|
52
52
|
projects/packages/ # @doki-land/nifty + platform @doki-land/nifty-*
|
|
53
|
-
scripts/ci/ # bind-publish-tag.mjs,
|
|
53
|
+
scripts/ci/ # bind-publish-tag.mjs, check-rust-dependency-policy.mjs, require-ci-success.mjs
|
|
54
54
|
```
|
|
55
55
|
|
|
56
56
|
Do **not** confuse npm-tools `legion` / Valkyrie with Nifty. Nifty is independent Node-API + TypeScript CLI tooling.
|
|
@@ -15,10 +15,10 @@ Every commit **subject** (first line) must:
|
|
|
15
15
|
2. Use an **English** imperative phrase after the gitmoji (project convention for publish repos)
|
|
16
16
|
3. Match `gitmoji + body` formatting rules enforced by `nifty lint`
|
|
17
17
|
|
|
18
|
-
Known gitmojis (Nifty default set):
|
|
18
|
+
Known gitmojis (Nifty default set, matches `nifty-types/src/gitmoji.rs`):
|
|
19
19
|
|
|
20
20
|
```text
|
|
21
|
-
✨ 🎨 🚀 🐛 🚑 🔥 💥 ♻️ 🔧 📝 👷 🧹 ⬆️ 🧪 🔨 📦 📌
|
|
21
|
+
✨ 🎨 🚀 🐛 🚑 🔥 💥 ♻️ 🔧 📝 👷 🧹 ⬆️ 🧪 🔨 📦 🎂 🎉 🚧 🚫 💄 🎀 ⚡ 🔒 📌
|
|
22
22
|
```
|
|
23
23
|
|
|
24
24
|
`📌` is for dependency or version pins (for example locking a site to a published npm version).
|
|
@@ -26,9 +26,9 @@ Known gitmojis (Nifty default set):
|
|
|
26
26
|
## Commands
|
|
27
27
|
|
|
28
28
|
```bash
|
|
29
|
-
#
|
|
30
|
-
nifty lint --from v0.
|
|
31
|
-
nifty check --from origin/dev
|
|
29
|
+
# `lint` reports, `check` reports and exits non-zero on errors
|
|
30
|
+
nifty lint --from v0.1.9 --to HEAD
|
|
31
|
+
nifty check --from origin/dev --to HEAD
|
|
32
32
|
|
|
33
33
|
# Commit-only scan/audit (gitmoji + semver/semicolon/backtick hygiene)
|
|
34
34
|
nifty commit scan --from d25daeba^ --to HEAD
|
|
@@ -46,6 +46,13 @@ Flat `{ "abc12345": "message" }` is also accepted.
|
|
|
46
46
|
|
|
47
47
|
Hash prefixes must be **unique** within the rewrite range.
|
|
48
48
|
|
|
49
|
+
### Tags are never moved
|
|
50
|
+
|
|
51
|
+
`commit apply` does not retarget tags. When a tag points inside the rewritten range, the command prints a warning
|
|
52
|
+
listing every such tag, and the tag keeps pointing at the pre-rewrite commit. Re-create or manually review those tags
|
|
53
|
+
before drafting release notes — otherwise `nifty change-logs` may miss rewritten commits. There is no implicit tag
|
|
54
|
+
migration and no `tag retarget` command today.
|
|
55
|
+
|
|
49
56
|
## Retime
|
|
50
57
|
|
|
51
58
|
Spread author and committer timestamps across a window. Writes a **new branch** (default `time-travel`); current branch
|
|
@@ -80,5 +87,6 @@ commit apply/retime use gix object writes.
|
|
|
80
87
|
| `--dry-run` before `commit apply` | Force-push without user consent |
|
|
81
88
|
| Explicit `--ref` when HEAD is detached | Use `git rebase -i` when user asked for Nifty tools |
|
|
82
89
|
| Explain parent relink-only rows in dry-run | Amend commits with `git commit --amend` for bulk history fixes |
|
|
90
|
+
| Re-point affected tags manually after apply | Assume tags follow rewritten commits |
|
|
83
91
|
|
|
84
92
|
After apply, the user must force-update the target ref if it was already published.
|
|
@@ -43,11 +43,18 @@ nifty bump --dry-run
|
|
|
43
43
|
|
|
44
44
|
Aligns all `projects/crates/*/Cargo.toml` and `projects/packages/*/package.json` versions.
|
|
45
45
|
|
|
46
|
+
## Repository policy (read first)
|
|
47
|
+
|
|
48
|
+
In `npm-tools` and other VMZ-family repositories, real versions publish **only** through tag-triggered CI OIDC
|
|
49
|
+
(`.github/workflows/publish-npm.yml`). Local `nifty publish` is limited to `--dry-run` and `--placeholder` (never-published
|
|
50
|
+
`0.0.0` stubs). Local token/OTP auth is for `nifty trust` setup and for consumer projects that have no OIDC workflow, not
|
|
51
|
+
for releasing these repositories. If the tag or CI run fails, stop and report instead of publishing locally.
|
|
52
|
+
|
|
46
53
|
## npm publish and trust
|
|
47
54
|
|
|
48
|
-
**Default: publish the whole workspace.** Nifty walks packages in dependency order and **skips versions already on the
|
|
55
|
+
**Default for consumer workspaces: publish the whole workspace.** Nifty walks packages in dependency order and **skips versions already on the
|
|
49
56
|
registry** (cache + `npm view`). After a release you can run plain `nifty publish` again — only new or bumped packages
|
|
50
|
-
are uploaded.
|
|
57
|
+
are uploaded. Inside `npm-tools` itself, see the repository policy above.
|
|
51
58
|
|
|
52
59
|
```bash
|
|
53
60
|
nifty publish --dry-run
|
|
@@ -78,6 +85,7 @@ GitHub Actions OIDC can publish on the next tag. `nifty trust` uses `publish.pac
|
|
|
78
85
|
|
|
79
86
|
Local auth: `NPM_TOKEN`, `--npm-token`, `--otp`, or `--totp-secret` (see `nifty publish --help`). Trust uses the
|
|
80
87
|
registry API with bearer token from `NPM_TOKEN` or `~/.npmrc`. Add OTP/TOTP on 2FA accounts when the registry asks.
|
|
88
|
+
Per the repository policy above, these paths are not used for real releases in `npm-tools` or VMZ-family repos.
|
|
81
89
|
|
|
82
90
|
**npm-tools CI**: tag `vX.Y.Z` triggers `.github/workflows/publish-npm.yml`. The workflow stages native artifacts into
|
|
83
91
|
the platform packages and then runs `nifty publish` (OIDC, no long-lived token in YAML). Native `.node` files ship as
|
|
@@ -88,9 +96,9 @@ the platform packages and then runs `nifty publish` (OIDC, no long-lived token i
|
|
|
88
96
|
Output is a **draft index** for hand-editing release notes — not the published GitHub Release body.
|
|
89
97
|
|
|
90
98
|
```bash
|
|
91
|
-
nifty change-logs --version 0.
|
|
92
|
-
nifty change-logs --from v0.
|
|
93
|
-
nifty change-logs --version 0.
|
|
99
|
+
nifty change-logs --version 0.1.10
|
|
100
|
+
nifty change-logs --from v0.1.9 --to v0.1.10
|
|
101
|
+
nifty change-logs --version 0.1.10 --write
|
|
94
102
|
nifty change-logs --tags
|
|
95
103
|
nifty change-logs lookup --email you@example.com --fetch
|
|
96
104
|
```
|
|
@@ -100,17 +108,18 @@ Default paths: `documentation/maintenance/author-github.json`, `documentation/ma
|
|
|
100
108
|
## GitHub upload
|
|
101
109
|
|
|
102
110
|
```bash
|
|
103
|
-
nifty upload --release --dir dist --tag v0.
|
|
111
|
+
nifty upload --release --dir dist --tag v0.1.10 --token "$GITHUB_TOKEN"
|
|
104
112
|
nifty upload --pages --dir dist
|
|
105
113
|
nifty upload --both --dir dist --github-action
|
|
106
114
|
```
|
|
107
115
|
|
|
108
|
-
Platform `.node` binaries are **not** uploaded here —
|
|
116
|
+
Platform `.node` binaries are **not** uploaded here — the release workflow stages them and CI publishes them with
|
|
117
|
+
`nifty publish`.
|
|
109
118
|
|
|
110
119
|
## CI native staging (maintainers)
|
|
111
120
|
|
|
112
121
|
```bash
|
|
113
|
-
nifty install-native --from
|
|
122
|
+
nifty install-native --from path/to/native-artifacts
|
|
114
123
|
```
|
|
115
124
|
|
|
116
125
|
Then `nifty publish` includes staged `@doki-land/nifty-<platform>` packages.
|
|
@@ -120,7 +129,11 @@ Then `nifty publish` includes staged `@doki-land/nifty-<platform>` packages.
|
|
|
120
129
|
1. `nifty check` on commits since last tag
|
|
121
130
|
2. `nifty bump` (or explicit version)
|
|
122
131
|
3. Commit version bump, tag `vX.Y.Z`, push branch + tag
|
|
123
|
-
4.
|
|
132
|
+
4. Push the tag and let CI publish (OIDC). Do not run a real-version `nifty publish` locally
|
|
124
133
|
5. **`nifty trust`** for any **new** package name not yet on the Trusted Publisher list
|
|
125
134
|
6. `nifty change-logs --version X.Y.Z --write` for reference draft
|
|
126
135
|
7. `nifty upload --release …` when generic assets need GitHub Release upload
|
|
136
|
+
|
|
137
|
+
If history was rewritten with `nifty commit apply`, tags inside that range still point at the pre-rewrite commits
|
|
138
|
+
(apply warns and never moves them). Re-create those tags before step 6 — `nifty change-logs` derives its range from
|
|
139
|
+
tags and would otherwise miss rewritten commits.
|
/package/{README.md → readme.md}
RENAMED
|
File without changes
|