actions-warden 0.1.0 → 0.1.1

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.
Files changed (2) hide show
  1. package/README.md +53 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -185,6 +185,39 @@ making findings visible directly in the GitHub UI.
185
185
  which fails the job by default. To collect findings without failing the build,
186
186
  set `continue-on-error: true` on the step.
187
187
 
188
+ ## Use it from Claude Code
189
+
190
+ This repo is also a Claude Code plugin. Once installed, Claude will invoke
191
+ `actions-warden` automatically whenever a prompt asks to audit, pin, or
192
+ upgrade GitHub Actions workflows.
193
+
194
+ **Option A - via the plugin marketplace (recommended):**
195
+
196
+ ```
197
+ /plugin marketplace add chiz0me/claude-plugins
198
+ /plugin install actions-warden@chiz0me
199
+ ```
200
+
201
+ **Option B - drop the skill in directly (no marketplace):**
202
+
203
+ ```sh
204
+ mkdir -p ~/.claude/skills/actions-warden
205
+ curl -fsSL https://raw.githubusercontent.com/chiz0me/actions-warden/main/skills/actions-warden/SKILL.md \
206
+ -o ~/.claude/skills/actions-warden/SKILL.md
207
+ ```
208
+
209
+ After installation, prompts like *"audit my workflows"*, *"pin my actions to
210
+ SHAs"*, or *"check this workflow for script injection"* will route through the
211
+ skill, which runs the CLI via `npx actions-warden` and explains the TOON
212
+ output back to you.
213
+
214
+ Plugin layout (per the Claude Code plugin spec):
215
+
216
+ ```
217
+ .claude-plugin/plugin.json # plugin manifest
218
+ skills/actions-warden/SKILL.md # the skill itself
219
+ ```
220
+
188
221
  ## Programmatic API
189
222
 
190
223
  Each command is also exported as an async function, so an LLM agent or
@@ -283,6 +316,26 @@ After the first release tag is pushed, open the release on github.com and tick
283
316
  "Publish this Action to the GitHub Marketplace" to list it. No automation
284
317
  required - the release workflow above handles everything except that opt-in.
285
318
 
319
+ ### Marketplace sync
320
+
321
+ When a `vX.Y.Z` tag is pushed, the `sync-marketplace` job in `release.yml`
322
+ updates the `actions-warden` plugin entry in
323
+ [chiz0me/claude-plugins/.claude-plugin/marketplace.json](https://github.com/chiz0me/claude-plugins/blob/main/.claude-plugin/marketplace.json)
324
+ to match. No-op when the marketplace is already on the target version.
325
+
326
+ **One-time setup (cross-repo write requires a token the default
327
+ `GITHUB_TOKEN` cannot provide):**
328
+
329
+ 1. Create a **fine-grained personal access token** at
330
+ https://github.com/settings/personal-access-tokens/new with:
331
+ - Repository access: **Only select repositories → `chiz0me/claude-plugins`**
332
+ - Permissions: **Contents: Read and write**
333
+ 2. In `chiz0me/actions-warden` repo settings, add it as an Actions secret
334
+ named **`MARKETPLACE_SYNC_TOKEN`**.
335
+
336
+ After that, every release tag also writes a `sync: bump actions-warden to vX.Y.Z`
337
+ commit to the marketplace repo.
338
+
286
339
  ### Publishing to npm
287
340
 
288
341
  The release workflow includes a `publish-npm` job that publishes to npm with
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "actions-warden",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Audit, pin, and upgrade GitHub Actions workflows. LLM-friendly TOON output, safe-by-default.",
5
5
  "author": "Naveen Yagati",
6
6
  "homepage": "https://github.com/chiz0me/actions-warden#readme",