[self-care:reactive-ui] Correct reactive-ui skill guidance on element intent

Abierto Apto para principiantes
  • ¿Algo no está bien?
#20,398 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
82/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, javascript
Área
developer-experience

Línea de trabajo

Lee .github/skills/reactive-ui/SKILL.md junto con dashboard/site/src/specification.js y dashboard/site/src/validator-pages.js. Comprueba que las indicaciones de la skill sobre la intención del elemento coincidan con VIEW_KEYS y con la validación de intent a nivel de página. La tarea está terminada cuando la redacción esté corregida y sea coherente con esas definiciones.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

agentic-workflows self-care self-care:reactive-ui-expert

[!TIP]
Your pull request is ready to create! 🎉 ✅

Everything is OK—the changes have been pushed to a branch. Please review the protected files, then create the pull request when you are ready.

Create the pull request

The original pull request description is below.

The reactive-ui skill told authors to record an intent on named UI elements. Views have no intent key, so that guidance contradicted the validator. This PR corrects the skill and changes nothing else.

Action: Maintainer should review the one-line skill wording change. Acceptance check: it matches VIEW_KEYS and the page-level intent validation.

Evidence
  • VIEW_KEYS in dashboard/site/src/specification.js has subject, objective and acceptance, but no intent.
  • dashboard/site/src/validator-pages.js validates intent only as a page field.
  • docs/dashboard-language-specification.md lists intent under page fields only.
  • No eligible pure-declarative view-source migration was found. The candidate sources are canonical database queries already declared in database.json, or synthetic runtime sources (simulation-days, cli-*, and GitHub query sources) that JSON alone cannot replace. Because of that, I used the skill-drift fallback.
Validation
  • Documentation-only change to .github/skills/reactive-ui/SKILL.md.
  • The dashboard test suites were not run because no JavaScript or dashboard JSON changed.
  • npm run compile could not run here because the gh aw extension is not installed. No workflow .md or manifest changed.
Control Plane

[!NOTE]
Protected files

This patch modifies protected files, which may affect project dependencies, CI/CD pipelines, or agent behaviour.

Protected files

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by SelfCare / Reactive UI Expert · copilot · auto · ~47 AIC · ⌖ ~1 AIC · ⊞ 16K · ◷

  • expires on Nov 15, 2026, 1:55 AM UTC
Lenguaje dominante
JavaScript
Estrellas
14
Forks
5
Merge medio
4 h 21 min
PR fusionados (30 d)
633

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/gh-cao

Todos los issues de githubnext/gh-cao

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.