com um clique
agentic-template
agentic-template contém 14 skills coletadas de tecnosor, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
GitLab CLI (glab) skill for GitLab interactions: create and review merge requests, manage issues, inspect pipelines, releases, and repository metadata directly from the terminal. Use whenever you need to interact with GitLab: open an MR, check pipeline status, create issues, list branches, merge MRs, or inspect releases. Keywords: gitlab, glab, MR, merge request, issue, release, pipeline, CI, merge, repo, branches, gitlab cli, gitlab pipelines, gitlab issues.
Manages kanban task creation, movement, and lifecycle across workspace repos. One file per task in kanban/tasks/{ID}.md with YAML frontmatter status field. Supports unlimited parallel DOING tasks, immutable Origin field, correct ID prefixes. Use when creating tickets, updating task status, or checking workflow health. Keywords: kanban, backlog, task, ticket, FEAT, FIX, CHORE, SCOUT, sprint, move task, update status, tarea, tablero, pendiente, en progreso.
Generates a structured read-only project status report from kanban files and code inspection. Provides health metrics, backlog depth, DOING count, recent completions, and blocked task summary. Does NOT write to kanban files. Use when asked for status, project health, sprint overview, or progress summaries. Keywords: status, health, progress, backlog, overview, metrics, sprint, blocked, report, estado, progreso, salud del proyecto, revisión, informe de estado.
Validates project build in strict sequential order: install dependencies, lint, compile, unit tests, integration tests. Stops on first failure and reports which step failed. Auto-detects project type (npm, Docker Compose, Terraform). Use before commits, PRs, or when verifying changes compile correctly. Keywords: build, compile, test, lint, verify, CI, npm, docker, terraform, construir, compilar, verificar, validar build.
Structured code review workflow: architecture boundaries, business logic correctness, test coverage, security, language compliance, and style. Outputs categorized findings as BLOCKING / WARNING / PASS. Read-only — never modifies code. Use when reviewing PRs, auditing existing code, or validating implementation against architecture rules. Keywords: review, code quality, architecture, PR, pull request, clean architecture, DDD, CQRS, boundaries, revisión de código, calidad, arquitectura, pull request.
EU regulatory compliance checklist covering GDPR (personal data protection), DORA (digital operational resilience), and PSD2 (payment services). Applies conditionally based on repo type — not all regulations apply to all services. Use when reviewing features that handle personal data, financial transactions, or digital payments. Keywords: GDPR, DORA, PSD2, compliance, privacy, audit, personal data, payments, regulation, EU, datos personales, cumplimiento normativo, privacidad, pagos.
Enforces Git Flow branch naming and commit message conventions. Use for branch creation, commit messages, PR descriptions, release planning, and hotfix workflows. Validates conventional commits format and git hygiene. Keywords: branch, feature, commit, PR, pull request, merge, release, ticket, hotfix, gitflow, rama, commit, parche, versión, flujo de trabajo.
GitHub CLI (gh) skill for all GitHub interactions: create and review PRs, manage issues, view repo info, manage releases, and run CI/CD workflows directly from the terminal. Use whenever you need to interact with GitHub: open a PR, check PR status, create issues, list branches, merge PRs, view CI runs, or set the default branch. Keywords: github, gh, PR, pull request, issue, release, workflow, CI, merge, repo, branches, actions, github cli, github actions, github pr, github issues.
Exhaustively inspects a repository's git history, documentation, database migrations, and test files to map completed work into kanban task files (status: done). Normalizes all entries to English. Creates backlog task files for incomplete work. Use when initializing kanban for a repo, onboarding, or auditing past work. Keywords: history, done, completed, git log, migrations, commits, audit, onboarding, initialize kanban, historial, completado, trabajo previo, auditoría.
Detects and fixes non-English content in source code, documentation, kanban files, agent files, and skill files. Reports violations as LANG-NNN entries. Auto-fixes comments and documentation after confirmation. Requires explicit confirmation for identifier renames (variable, method, class names). Never modifies i18n files, locales, or translation keys. Bilingual exception: agent/skill description fields may be bilingual for searchability. Keywords: English, language, Spanish, translation, comment, identifier, naming, idioma, inglés, español, comentarios, identificadores, nomenclatura.
Scaffolds a new Vue 3 page, component, or composable with i18n, accessibility (WCAG 2.1 AA), TypeScript strict, and Tailwind CSS 4. Use when implementing new UI views, reusable components, or shared composables. Keywords: Vue, component, page, composable, i18n, accessibility, a11y, WCAG, TypeScript, Tailwind, scaffold, componente, página, accesibilidad.
BLOCKING security checklist based on OWASP Top 10. Immediately stops task progression if critical violations found (secrets, injections, hardcoded credentials). Checks: no secrets in code, input validation at boundaries, injection prevention, no PII in logs, dependency CVEs, least privilege access. Use before every PR or when reviewing security-sensitive changes. Keywords: security, OWASP, secret, vulnerability, CVE, injection, API key, password, credential, token, PII, seguridad, vulnerabilidad, secreto, inyección, credencial.
Enforces TDD practices and test quality standards. Validates naming conventions, AAA structure, test isolation, and coverage minimums. Backend: Vitest. Frontend: Vitest + @vue/test-utils. Use when writing tests, reviewing test quality, or setting up a TDD workflow. Keywords: test, TDD, coverage, vitest, unit test, integration test, mock, prueba, cobertura, prueba unitaria, test-driven, AAA, arrange-act-assert.
Scaffolds a new CQRS command or query following the Vertical Slice pattern with handler, result, and test. TypeScript / Node.js version. Generates all files for a feature slice in src/application/features/. Use when implementing a new use case, feature, or business operation. Keywords: vertical slice, command, query, CQRS, handler, feature, use case, scaffold, vertical slice, comando, consulta, caso de uso.