tecnosor

eIDAS (Electronic Identification, Authentication and Trust Services) compliance checklist. Validates electronic identity, qualified signatures, trust services, and KYC/AML workflows. Use for banking KYC, digital onboarding, remote identification, and electronic signatures in the EU.

ISO 20022 financial messaging standard compliance checklist. Validates payment messages (pain, pacs, camt), schema compliance, XML validation, and end-to-end payment flows. Use for banking payment systems, real-time transfers, and cross-border payments.

SEPA (Single Euro Payments Area) compliance checklist. Validates SEPA Credit Transfer, SEPA Direct Debit, and SEPA Instant payments. Checks IBAN/BIC rules, scheme compliance, mandate management, and settlement timing. Use for euro payment processing in the EU/EEA.

DEPRECATED meta-skill. Use the individual compliance skills instead: gdpr, dora, mica, psd2, pci-dss. This skill now acts as a dispatcher that loads only the sub-skills applicable to the project scope.

DORA (Digital Operational Resilience Act) compliance checklist. Validates ICT risk management, incident reporting, resilience testing, third-party risk, and business continuity. Use for financial entities and ICT service providers in the EU.

GDPR (General Data Protection Regulation) compliance checklist. Validates data processing principles, data subject rights, encryption, PII handling, and privacy-by-design. Use when reviewing features that process personal data of EU residents.

Git workflow management following {{GIT_WORKFLOW}} strategy. Enforces branch naming conventions ({{BRANCH_NAMING}}), commit message format ({{COMMIT_CONVENTION}}), and proper merge/rebase practices. Use for all git operations: branching, committing, merging, and PR creation.

Jira issue management via MCP or REST API. Creates epics, stories, subtasks, and bugs. Updates status transitions, adds comments, links PRs. Supports Jira Cloud and Server. Use for all issue tracker operations during the SDLC workflow.

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.