Menu
SkillsMP has collected 17 skills from albertoirurueta/ai-catalog. Open a skill to review its source and details.
Showing 17 of 17 collected skills.
Set up the contract-first API layer of a Spring Boot service — the single `apis/` directory at the repository root holding every contract (`apis/rest-server/` OpenAPI specs, `apis/grpc-server/` protobuf definitions, `apis/graphql-server/` SDL schemas,…
Create the GitHub Actions workflows for a Spring Boot service repository — a build workflow (`build.yml`) that runs on pushes to the integration and main branches and on pull requests, executing unit tests via Surefire and Testcontainers-backed integration…
Scaffold the source tree of a DDD/hexagonal Spring Boot service whose Maven reactor already exists — the package layout for every module, the ports (interfaces) that `domain` defines, a worked adapter skeleton per `infrastructure`/`api` module (repository…
Generate the Maven reactor for a DDD/hexagonal Spring Boot service — the root `pom.xml` (the single place every dependency and plugin version is declared) plus one `pom.xml` per module (`domain`, `application`, `infrastructure/database/<engine>`,…
End-to-end bootstrap for a brand-new Spring Boot service repository built on DDD + hexagonal architecture as a Maven multi-module reactor (`boot`, `application`, `domain`, `infrastructure/*`, `api/*`). Collects the project's identity (groupId, artifactId,…
Set up the local-execution and integration-test infrastructure for a Spring Boot service — a `compose.yaml` at the repository root with one pinned service per technology the stack uses (MongoDB, Couchbase, PostgreSQL/pgvector, MariaDB, Elasticsearch, Neo4j,…
Generate the OpenTofu (Terraform-compatible) infrastructure-as-code that deploys a Spring Boot service to AWS or Google Cloud, derived from the technologies the service actually uses — a remote encrypted state backend, a keyless GitHub OIDC deployment role, a…
End-to-end bootstrap for a brand-new Java/Maven library repository — collects the project's identity (groupId, artifactId, base package, developer name/email/organizationUrl, license) and pipeline parameters (integration branch, Java version, publishing…
Analyze every Claude Code skill (`.claude/skills/*/SKILL.md`) and agent (custom definitions under `.claude/agents/*.md`, plus built-in agent types referenced from skills via the `Agent` tool) defined in this repository, and generate/update the Antora…
Compact the `knowledge/` base built by `iru-knowledge-process-inbox` — sweep `knowledge/pending` and `knowledge/agreements` for (a) duplicate pending tasks, removing the duplicates that have no tracker issue assigned while folding any extra context they…
Process every file in `knowledge/inbox` — meeting transcriptions (timestamped or not, diarized or
Summarize the most relevant agreements and pending tasks recorded in the `knowledge/` base (built by `iru-knowledge-process-inbox`) for a given subject. Accepts any mix of scoping context — a person (matched against `knowledge/people/*.md`), a meeting…
Convert one or more pending/not-completed agreements from the `knowledge/` base (built by `iru-knowledge-process-inbox`) into a GitHub issue. Asks the user which agreement(s) to convert, accepting a pending task id (`<timestamp>-<n>`), a…
Convert one or more pending/not-completed agreements from the `knowledge/` base (built by `iru-knowledge-process-inbox`) into a Jira ticket. Asks the user which agreement(s) to convert, accepting a pending task id (`<timestamp>-<n>`), a…
Mark one pending agreement/task as completed — given a task id matching a `knowledge/pending/pending-<task-id>.md` file, delete that pending file and check off the matching numbered item in its `knowledge/agreements/agreement-<timestamp>.md` file. Invoke as…
Create the `knowledge/` directory at the repository root with its five subdirectories — `inbox`, `meetings`, `people`, `agreements`, and `pending` — each containing a `.gitkeep` file so git tracks the empty directory. Invoke as `/iru-knowledge-setup`.…
Draft and file a new Jira ticket that is ready to be picked up by the `/iru-issue`, `/iru-plan`, `/iru-code` flow. Runs the `iru-explore` skill first to ground the ticket in the actual codebase, then asks the user for the purpose of the task to be…