oh-my-customcodex 0.3.0 → 0.3.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.
package/dist/cli/index.js CHANGED
@@ -3091,7 +3091,7 @@ var init_package = __esm(() => {
3091
3091
  workspaces: [
3092
3092
  "packages/*"
3093
3093
  ],
3094
- version: "0.3.0",
3094
+ version: "0.3.1",
3095
3095
  description: "Batteries-included agent harness on top of GPT Codex + OMX",
3096
3096
  type: "module",
3097
3097
  bin: {
package/dist/index.js CHANGED
@@ -2180,7 +2180,7 @@ var package_default = {
2180
2180
  workspaces: [
2181
2181
  "packages/*"
2182
2182
  ],
2183
- version: "0.3.0",
2183
+ version: "0.3.1",
2184
2184
  description: "Batteries-included agent harness on top of GPT Codex + OMX",
2185
2185
  type: "module",
2186
2186
  bin: {
package/package.json CHANGED
@@ -3,7 +3,7 @@
3
3
  "workspaces": [
4
4
  "packages/*"
5
5
  ],
6
- "version": "0.3.0",
6
+ "version": "0.3.1",
7
7
  "description": "Batteries-included agent harness on top of GPT Codex + OMX",
8
8
  "type": "module",
9
9
  "bin": {
@@ -1,6 +1,6 @@
1
1
  # Pipeline Registry
2
2
 
3
- description: Registry of available pipelines for sequential workflows
3
+ description: Registry of available workflow templates for the /pipeline skill
4
4
 
5
5
  pipelines:
6
6
  - name: code-review
@@ -13,6 +13,7 @@ templates:
13
13
  description: Base template for creating new pipelines
14
14
 
15
15
  usage:
16
- run: "pipeline:run <name> --input key=value"
17
- list: "pipeline:list"
18
- create: "Use templates/pipeline-template.yaml as base"
16
+ run: "/pipeline <name>"
17
+ list: "/pipeline"
18
+ resume: "/pipeline resume"
19
+ create: "Create workflows/<name>.yaml from templates/pipeline-template.yaml"
@@ -1,6 +1,6 @@
1
1
  {
2
- "version": "0.3.0",
3
- "lastUpdated": "2026-04-20T06:05:00.000Z",
2
+ "version": "0.3.1",
3
+ "lastUpdated": "2026-04-22T03:55:00.000Z",
4
4
  "components": [
5
5
  {
6
6
  "name": "rules",
@@ -1,8 +1,8 @@
1
1
  # /pipeline auto-dev — Full-auto release pipeline
2
- # Pre-triages open issues → triage verify-done → plan → implement → verify → PR → followup
2
+ # Pre-triages open issues → triage verify-done → plan → implement → verify → PR/releasepublish → followup
3
3
 
4
4
  name: auto-dev
5
- description: "Full-auto release pipeline: pre-triage → triage → plan → implement → verify → PR → followup"
5
+ description: "Full-auto release pipeline: pre-triage → triage → plan → implement → verify → PR → publish → followup"
6
6
  mode: auto
7
7
  error: halt-and-report
8
8
 
@@ -41,6 +41,27 @@ steps:
41
41
  prompt: "Create release branch and pull request"
42
42
  description: Create release branch and pull request
43
43
 
44
+ - name: publish
45
+ prompt: |
46
+ Publish the validated release artifact after the release PR/branch stage.
47
+
48
+ Project-specific behavior:
49
+ - npm package:
50
+ 1. Confirm package name and current version from package.json
51
+ 2. Check registry state (`npm view <pkg> version`)
52
+ 3. If version is unchanged but release-worthy, bump semver intentionally
53
+ 4. Run the publish path (`npm publish` or the repo's release workflow trigger)
54
+ 5. Verify registry publication (`npm view <pkg> version`)
55
+ - GitHub-release artifact project:
56
+ 1. Create/push tag if required
57
+ 2. Trigger or create the release artifact
58
+ 3. Verify the release exists and assets are available
59
+
60
+ Halt and report on auth, versioning, or publish verification failures.
61
+ description: Publish the release artifact and verify external availability
62
+ depends_on: release
63
+
44
64
  - name: followup
45
65
  skill: post-release-followup
46
66
  description: Recommend follow-up actions — user chooses to execute now or register as issues
67
+ depends_on: publish