all publishers

EdgardoAcosta

@edgardoacosta source repo

5 published skills

  1. ▌
    Bump Core Pkg · edgardoacosta bundle
    Bump manufacturing-core-pkg in the ef-manufacturing host to a released tag and push main (staging deploy). Use when Edgardo says "new version of core vX.Y.Z", "bump core", "deploy core to staging". Looks up the latest tags, confirms the tag with him, regenerates composer.json/lock from HEAD, commits "Bump manufacturing-core-pkg to vX.Y.Z" with no co-author and pushes main only. Never tags or releases the host.
    0 installs
  2. ▌
    Manufacturing · edgardoacosta bundle
    EnviaFlores Manufacturing migration context and playbooks. Use for anything about the manufacturing team or its GitHub project 59 - creating or filling Epic/Story/Task/Bug issues, researching legacy screens (talleres, suministros, OPS, admin-api), Grafana/Loki/Tempo telemetry for ef-manufacturing or the app backend, checking what each dev (Jorge, Julio, Guillermo, Dali) is working on or whether they have tasks, assigning QA, reading the Notion migration databases or the Obsidian manufacturing notes, reviewing/testing teammates' PRs, shipping (commit/PR, core-pkg release, host composer bump, permissions), and the workshop print servers (workshop-daemon, labeler, Zebra/CUPS queues, ZPL label templates, etiquetas QR, print server deploys and "users can't print" diagnosis).
    0 installs
  3. ▌
    Boui Adminlte Migration Conventions · edgardoacosta
    Conventions for migrating legacy AdminLTE admin screens into BOUI/Uxmal. Use when a developer needs practical guidance to reinterpret AdminLTE pages using Uxmal Design System 2026, BOUI components, Laravel page structure, and clear backoffice UX patterns without requiring pixel-perfect validation or specialized tooling.
    0 installs
  4. ▌
    Legacy Pr UI Review · edgardoacosta
    Review and test changes that port a legacy screen into manufacturing-core-pkg — either a PR (ours or a teammate's) or local code not pushed yet (a bug branch, uncommitted work). Legacy is the source of truth, every claim is validated against legacy code or the DB, the definitive test is a Playwright run on the real screen, and the output is a pass/fail matrix. Use when the user asks to "test this PR", "review Julio's/Jorge's changes", "test my changes", "is the fix done?", "run the full test", or "run the Obsidian bug list against this screen".
    0 installs
  5. ▌
    Cbq Concurrency Test · edgardoacosta bundle
    Concurrent live test (real HTTP calls, NOT Pest) of every command in manufacturing-core-pkg that uses the EventCommands/CBQ toolkit — inventory movements over Kafka, idempotency, redelivery, and the Redis commands. Use when the user asks to "test all the commands", "run the concurrency test", "check the engines still work" after changes to the toolkit or the engines.
    0 installs