@pasosdejesus/mpdj 0.3.4 → 0.3.5

package/SKILL.md

@@ -343,6 +343,29 @@ Full recipe: [doc/engines.md](../../doc/engines.md) §12; release ritual:
 ./bin/m m:man [--out <file>]     # Generates the mdoc manual page
 ```
 
+### Requirements Commands
+
+```bash
+./bin/m req:list                     # Local REQ/ with status
+./bin/m req:show <N>                 # One requirement
+./bin/m req:cross                    # Requirements affecting other projects
+./bin/m req:compare [N]              # Local vs remote, Sync: sync | loc+ | rem+
+./bin/m req:sync-to-repo [N ...]     # No N: pushes every loc+ and creates missing issues
+./bin/m req:sync-from-repo [N ...]   # No N: pulls every rem+ and creates remote-only REQs
+./bin/m req:list-repo                # Open remote issues
+./bin/m req:create "<título>" [tipo] # Remote issue + local REQ
+./bin/m req:close <N>                # Sync, close the issue, delete the local file
+```
+
+`req:*` reads `REQ/` from the current directory and needs no generated project.
+`req:compare` classifies with the same function the sync commands use, so its `Sync`
+column is the plan: `loc+` goes up with `req:sync-to-repo`, `rem+` comes down with
+`req:sync-from-repo`, `sync` is left alone, and issues with no local REQ appear as
+remote-only (a new clone catches up with `req:sync-from-repo`). Only the operator runs
+the writing commands (`req:sync-to-repo`, `req:close`); they need `GITLAB_TOKEN` or
+`~/.config/m/gitlab-token`, while `req:sync-from-repo` reads with public access when
+there is no token. See [REQ/README.md](../../REQ/README.md).
+
 ### Environment Commands
 
 ```bash

package/dist/SKILL.md

@@ -343,6 +343,29 @@ Full recipe: [doc/engines.md](../../doc/engines.md) §12; release ritual:
 ./bin/m m:man [--out <file>]     # Generates the mdoc manual page
 ```
 
+### Requirements Commands
+
+```bash
+./bin/m req:list                     # Local REQ/ with status
+./bin/m req:show <N>                 # One requirement
+./bin/m req:cross                    # Requirements affecting other projects
+./bin/m req:compare [N]              # Local vs remote, Sync: sync | loc+ | rem+
+./bin/m req:sync-to-repo [N ...]     # No N: pushes every loc+ and creates missing issues
+./bin/m req:sync-from-repo [N ...]   # No N: pulls every rem+ and creates remote-only REQs
+./bin/m req:list-repo                # Open remote issues
+./bin/m req:create "<título>" [tipo] # Remote issue + local REQ
+./bin/m req:close <N>                # Sync, close the issue, delete the local file
+```
+
+`req:*` reads `REQ/` from the current directory and needs no generated project.
+`req:compare` classifies with the same function the sync commands use, so its `Sync`
+column is the plan: `loc+` goes up with `req:sync-to-repo`, `rem+` comes down with
+`req:sync-from-repo`, `sync` is left alone, and issues with no local REQ appear as
+remote-only (a new clone catches up with `req:sync-from-repo`). Only the operator runs
+the writing commands (`req:sync-to-repo`, `req:close`); they need `GITLAB_TOKEN` or
+`~/.config/m/gitlab-token`, while `req:sync-from-repo` reads with public access when
+there is no token. See [REQ/README.md](../../REQ/README.md).
+
 ### Environment Commands
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pasosdejesus/mpdj",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "description": "Extensión Pasos de Jesús para m CLI — marco cristiano, credenciales, requerimientos",
   "author": "",
   "license": "ISC",
@@ -64,7 +64,7 @@
     "REQ"
   ],
   "peerDependencies": {
-    "@pasosdejesus/m": "^0.37.14",
+    "@pasosdejesus/m": "^0.37.15",
     "next": ">=15.0.0",
     "react": ">=18.0.0",
     "vitest": ">=2.1.9"