@avantmedia/af 0.0.3 → 0.0.4

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/package.json +1 -1
  2. package/setup/.claude/commands/commit-work.md +1 -6
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@avantmedia/af",
3
- "version": "0.0.3",
3
+ "version": "0.0.4",
4
4
  "description": "Development utility.",
5
5
  "homepage": "https://github.com/avantmedialtd/artifex#readme",
6
6
  "bugs": {
package/setup/.claude/commands/commit-work.md CHANGED
@@ -29,12 +29,7 @@ Examples:
29
29
 
30
30
  2. **Archive the OpenSpec change (if not already archived):**
31
31
  - Check if `openspec/changes/<id>/` directory exists
32
- - If it exists, perform the OPSX archive workflow:
33
- 1. Check artifact completion: `openspec status --change "<id>" --json`
34
- 2. Check task completion: read `openspec/changes/<id>/tasks.md`, count `- [ ]` vs `- [x]`
35
- 3. Check for delta specs at `openspec/changes/<id>/specs/` — if they exist, perform agent-driven sync to main specs (same as `/opsx:sync`)
36
- 4. Archive: `mkdir -p openspec/changes/archive && mv openspec/changes/<id> openspec/changes/archive/YYYY-MM-DD-<id>`
37
- 5. Ensure everything meets the project's formatting rules (run `bun run format` if needed)
32
+ - If it exists, invoke `/opsx:archive <id>`
38
33
  - If the directory does not exist (already archived), skip this step
39
34
 
40
35
  3. Run the following command to stage all changes and create a commit: