gleap-analyzer
Gleap Card Analyzer (N3 Support)
Uses the Gleap MCP server (mcp__gleap__* tools) to fetch ticket data. The MCP handles authentication and project scoping — no GLEAP_API_KEY or projectId is required from the consumer project.
Workflow
1. Get the Gleap card URL
Ask the user for the Gleap card URL if not already provided.
URL format: https://app.gleap.io/projects/{projectId}/{channel}/{ticketId}
Extract the ticketId (last path segment, 24-char hex). The projectId is not needed because the MCP is already scoped to a project.
Input validation — Verify ticketId matches /^[0-9a-f]{24}$/i. If it doesn't, stop and ask the user for a valid Gleap URL.
2. Fetch card data via MCP
Call these three tools in parallel:
More from leofalco/shared-skills
gleap-responder
>
4angular-upgrade
>
2flux-publish
Cria um card no board "Produto FSM - Publicações" no Flux a partir do PR da branch atual. Use sempre que o usuário pedir "cria card de publicação", "vira esse PR em card no Flux", "manda esse PR pro flux", "abre publicação", "fluxa esse PR", ou variações — incluindo logo depois de mergear um PR, quando faz sentido publicar.
2