@imolko/ultra-agent 0.1.0-beta → 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 +87 -58
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,93 +1,122 @@
1
- # ultra-ai-coding
1
+ # @imolko/ultra-agent
2
2
 
3
+ La **metodología ultra** como paquete versionado: el conjunto canónico de
4
+ *skills*, el registro de ADRs A/T/P, las extensiones de pi y un CLI para
5
+ instalarla, actualizarla y mantenerla sin deriva.
3
6
 
7
+ `@imolko/ultra-agent` es la fuente única de la metodología ([A-052](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/foundational/A-052-distribucion-metodologia-paquete-versionado.md)).
8
+ Los repositorios consumidores la instalan y la leen desde aquí, en lugar de
9
+ duplicar skills, ADRs o guardrails.
4
10
 
5
- ## Getting started
11
+ ## Requisitos
6
12
 
7
- To make it easy for you to get started with GitLab, here's a list of recommended next steps.
13
+ - **Node.js ≥ 20**.
14
+ - [pi coding agent](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)
15
+ (peer dependency) para usar los skills y las extensiones.
8
16
 
9
- Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
17
+ ## Instalación
10
18
 
11
- ## Add your files
19
+ ```bash
20
+ # instala la metodología en el repositorio actual
21
+ npx @imolko/ultra-agent install
22
+ ```
12
23
 
13
- * [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
14
- * [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
24
+ O como dependencia de desarrollo:
15
25
 
16
- ```
17
- cd existing_repo
18
- git remote add origin https://gitlab.com/imolko/ultra-stack/ultra-agent.git
19
- git branch -M main
20
- git push -uf origin main
26
+ ```bash
27
+ npm install --save-dev @imolko/ultra-agent
21
28
  ```
22
29
 
23
- ## Integrate with your tools
30
+ `install` materializa en el consumidor:
24
31
 
25
- * [Set up project integrations](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/settings/integrations)
32
+ - un **espejo de solo lectura** de los ADRs A/T/P (+ `ADR-0000` y el gate de
33
+ consistencia),
34
+ - el **pointer hub** `docs/agents/repo-config.md` con los punteros del repo
35
+ (`adr_dir`, `domain_dir`, `issue_language`, `tracker_cli`, `ship_cmd`),
36
+ - el bloque `## Agent skills` que ancla `AGENTS.md` / `CLAUDE.md` al hub,
37
+ - el **manifiesto** `docs/agents/manifest.json` (versión instalada + hashes) que
38
+ permite detectar deriva.
26
39
 
27
- ## Collaborate with your team
40
+ ## CLI
28
41
 
29
- * [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
30
- * [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
31
- * [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
32
- * [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
33
- * [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
42
+ El binario es `ultra-agent`.
34
43
 
35
- ## Test and Deploy
44
+ | Comando | Qué hace |
45
+ |---------|----------|
46
+ | `ultra-agent install [--dest <dir>]` | Materializa el espejo A/T/P + gate, el pointer hub y el manifiesto. |
47
+ | `ultra-agent update [--dest <dir>] [--reset]` | Reconcilia el espejo y **falla ante deriva**; `--reset` respalda y restaura. |
48
+ | `ultra-agent status [--dest <dir>]` | Reporta la versión instalada y si hay deriva. |
49
+ | `ultra-agent init-lint [--dest <dir>]` | Escribe el andamiaje de lint del consumidor (`eslint.config.mjs` + `.pi/qa-guardrail.json`) sin sobrescribir lo existente. |
50
+ | `ultra-agent ship <flags>` | Dispara el pipeline *ship* sobre un spec y sus issues hijos ([A-039](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/foundational/A-039-pipeline-ship-issues-hijos-spec.md)). |
51
+ | `ultra-agent version` | Imprime la versión del paquete. |
52
+ | `ultra-agent help` | Muestra la ayuda. |
36
53
 
37
- Use the built-in continuous integration in GitLab.
54
+ `--dest <dir>` apunta a otro directorio (por defecto, el directorio actual).
38
55
 
39
- * [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
40
- * [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
41
- * [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
42
- * [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
43
- * [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
56
+ ## Qué incluye
44
57
 
45
- ***
58
+ ### Skills canónicos
46
59
 
47
- # Editing this README
60
+ 19 skills que el agente descubre por la `description` de cada `SKILL.md`
61
+ ([A-034](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/foundational/A-034-canonical-skill-set.md)):
48
62
 
49
- When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
63
+ `code-review`, `codebase-design`, `configure-repo`, `diagnose-bug`,
64
+ `domain-modeling`, `grill-me`, `i-have-an-idea`, `implement`, `research`,
65
+ `ship`, `spike`, `tdd`, `to-specs`, `to-tasks`, `triage`, `ultra-generator`,
66
+ `wayfinder`, `workflow`, `writing-for-agents`.
50
67
 
51
- ## Suggestions for a good README
68
+ ### Registro de ADRs
52
69
 
53
- Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
70
+ Decisiones de arquitectura en tres tiers, más el meta-ADR de proceso:
54
71
 
55
- ## Name
56
- Choose a self-explaining name for your project.
72
+ - **A — fundacional**: decisiones agnósticas al lenguaje.
73
+ - **T — TypeScript**: ecosistema TypeScript/Zod/Node.js.
74
+ - **P — Python**: ecosistema Python.
75
+ - **ADR-0000**: proceso y formato de los ADRs.
57
76
 
58
- ## Description
59
- Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
77
+ El espejo se copia como **solo lectura**: el tier de proyecto y los READMEs de
78
+ dominio del consumidor nunca se tocan.
60
79
 
61
- ## Badges
62
- On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
80
+ ### Extensiones de pi
63
81
 
64
- ## Visuals
65
- Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
82
+ - **handoff** — genera un documento de traspaso de contexto, renombra la sesión
83
+ y arranca una sesión nueva sembrada con el handoff.
84
+ - **qa-guardrail** — el bucle de linting del agente pi
85
+ ([A-045](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/foundational/A-045-guardrails-aplicables-no-directrices.md),
86
+ [A-049](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/foundational/A-049-materializacion-bucle-guardrails-extension-nativa-pi.md)):
87
+ lintea **solo el delta** de cada edición y corta tras N fallos consecutivos.
66
88
 
67
- ## Installation
68
- Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
89
+ ## Versionado y canales
69
90
 
70
- ## Usage
71
- Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
91
+ La versión se deriva de los tipos de *Conventional Commits*
92
+ ([A-033](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/foundational/A-033-estandar-mensajes-commit.md)):
93
+ `feat` → *minor*, `fix` → *patch*, breaking → *major*.
72
94
 
73
- ## Support
74
- Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
95
+ - `develop` publica el canal **`beta`**.
96
+ - `main` publica el canal **`latest`** (estable).
75
97
 
76
- ## Roadmap
77
- If you have ideas for releases in the future, it is a good idea to list them in the README.
98
+ La publicación usa **Trusted Publishing (OIDC)** en runners alojados, con
99
+ *fallback* automático por **staging** (token de mínimo privilegio + aprobación
100
+ 2FA) en runners propios
101
+ ([T-025](https://gitlab.com/imolko/ultra-stack/ultra-agent/-/blob/develop/docs/adr/typescript/T-025-publicacion-npm-trusted-publishing-procedencia.md)).
102
+ Las etiquetas git se reconcilian desde el `gitHead` del registry.
78
103
 
79
- ## Contributing
80
- State if you are open to contributions and what your requirements are for accepting them.
104
+ ## Desarrollo
81
105
 
82
- For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
106
+ ```bash
107
+ npm install
108
+ npm test # vitest
109
+ npm run typecheck # tsc --noEmit
110
+ npm run gate # gate de consistencia del registro ADR
111
+ npm run build # compila a dist-node/ y copia assets
112
+ ```
83
113
 
84
- You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
114
+ ## Enlaces
85
115
 
86
- ## Authors and acknowledgment
87
- Show your appreciation to those who have contributed to the project.
116
+ - Repositorio: <https://gitlab.com/imolko/ultra-stack/ultra-agent>
117
+ - Registro de ADRs: <https://gitlab.com/imolko/ultra-stack/ultra-agent/-/tree/develop/docs/adr>
118
+ - Incidencias: <https://gitlab.com/imolko/ultra-stack/ultra-agent/-/issues>
88
119
 
89
- ## License
90
- For open source projects, say how it is licensed.
120
+ ## Licencia
91
121
 
92
- ## Project status
93
- If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
122
+ MIT © Imolko
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@imolko/ultra-agent",
3
- "version": "0.1.0-beta",
3
+ "version": "0.1.1",
4
4
  "description": "Metodología ultra como paquete versionado: skills canónicos, registro ADR A/T/P, extensiones de pi y CLI (install/update/status/ship).",
5
5
  "license": "MIT",
6
6
  "author": {