linuxfoundation
- 94 skills
- 0 followers
- 23 hours ago last updated
- ▌ Speckit Tasks · linuxfoundationGenerate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
- ▌ Speckit Specify · linuxfoundationCreate or update the feature specification from a natural language feature description.
- ▌ Vue · linuxfoundation bundleUse when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
- ▌ Nuxt · linuxfoundation bundleUse when working on Nuxt 4+ projects - provides server routes, file-based routing, middleware patterns, Nuxt-specific composables, and configuration with latest docs. Covers h3 v1 helpers (validation, WebSocket, SSE) and nitropack v2 patterns. Updated for Nuxt 4.3+.
- ▌ Uikit · linuxfoundation bundleUse when building any UI element in the crowdfunding frontend — covers when to use existing uikit components, how to extend them, and when to ask before creating new ones
- ▌ Populate Jtbds · linuxfoundationPopulate @fgadoc:jtbd annotations in the OpenFGA model by scraping live API authorization rules from the dev Kubernetes cluster and synthesizing JTBD statements. Use when the model has new types or relations that need JTBD annotations refreshed.
- ▌ Helm Local Stack · linuxfoundationUse when the user wants to bring up the local LFX platform stack, edit the OpenFGA authorization model and re-render permissions docs, update platform chart dependencies, or debug local stack install/sync issues. Fires on "bring up local LFX platform", "edit OpenFGA model", "update platform chart dependencies", "debug local stack".
- ▌ Render Permissions · linuxfoundationRender PERMISSIONS.md from @fgadoc annotations in the OpenFGA model. Use after any change to model.fga to keep the human-readable permissions reference in sync.
- ▌ Meeting Service Code Review · linuxfoundationHow to judge the implementation of an lfx-v2-meeting-service pull request: the line-level grounding method, the quality dimensions, the traps specific to this Goa service's two surfaces (the ITX proxy and the v1 KV event pipeline), and the security anchors for meeting join credentials, visibility, and PII. Use on every PR that changes code, however small.
- ▌ Meeting Service Code Reviewer · linuxfoundationRepo-owned code-review skill for lfx-v2-meeting-service, the repo-code role of this repo's local pre-PR review. Audits one commit or range against this repo's written rule surface — CLAUDE.md, the FGA/indexer/event-processing/ITX contract docs, the Goa design boundary, and the chart — and returns a Markdown review in which every finding quotes the rule it cites. Loaded under its exact `/meeting-service-code-reviewer` name by the `/lfx-skills:lfx-local-review` lifecycle; not a skill a developer invokes by hand.
- ▌ Meeting Service Learnings Reviewer · linuxfoundationRepo-owned learnings-review skill for lfx-v2-meeting-service, the repo-learnings role of this repo's local pre-PR review. Matches one commit or range against this repo's knowledge base of patterns extracted from real past PR review comments, applies the known-false-positive floor last, and returns a Markdown review in which every finding quotes its KB entry. Loaded under its exact `/meeting-service-learnings-reviewer` name by the `/lfx-skills:lfx-local-review` lifecycle; not a skill a developer invokes by hand.
- ▌ Email Service Dev · linuxfoundation bundleRepo-local Go coding conventions and implementation guidance for lfx-v2-email-service. Auto-attaches when editing Go code, NATS subjects and payloads, SMTP/SES/SQS tracking code, Makefile, Helm chart templates, or service-owned docs. Owns the email-service public NATS contract, tracking KV behavior, SMTP sender boundary, SES engagement poller, tests, formatting, linting, and license headers. Central platform composition stays in lfx-skills:lfx-platform-architecture; cross-repo routing stays in lfx-skills:lfx.
- ▌ Email Service Preflight · linuxfoundationRepo-local mechanical pre-PR pipeline for lfx-v2-email-service. Runs Go working-tree checks, license headers, formatting, lint, build, tests, protected-file reporting, commit verification, and PR change summary. Run after /email-service-pr-readiness.
- ▌ Email Service Pr Readiness · linuxfoundationRepo-local pre-PR shape check for lfx-v2-email-service. Audits only branch and PR hygiene: branch name, JIRA reference, conventional commits, rebase status, DCO plus GPG signing, total diff size, and email-service protected files. Does not audit Go code or architecture. Run before /email-service-preflight.
- ▌ Email Service Code Reviewer · linuxfoundationPost-commit code-convention audit for lfx-v2-email-service. Audits the latest commit in the email service repo against the repo-owned documented rule surface: CLAUDE.md, .claude/skills/email-service-dev, pr-readiness/preflight boundaries, README/docs, public pkg/api contract, cmd/internal layout, Makefile, and chart docs. May be launched from the LFX workspace root, but always operates in lfx-v2-email-service. Every repo-convention finding quotes a loaded source. Pass the keyword `branch` to switch to full-branch mode (audits origin/main...HEAD). Invoke after every pre-PR commit in parallel with lfx-skills:lfx-general-code-reviewer.
- ▌ Email Service Learnings Reviewer · linuxfoundationPost-commit empirical-pattern review for lfx-v2-email-service. Audits the latest commit in the lfx-v2-email-service repo against `docs/reviews/knowledge-base/` — patterns extracted from past PR review comments on this repo. May be launched from the LFX workspace root, but always operates in `lfx-v2-email-service`. Findings are gated by KB matches: every finding must quote a pattern entry; unsourced findings are dropped. Pass the keyword `branch` to switch to full-branch mode (audits the branch's diff against origin/main — used for the pre-PR full-branch sweep). Renders a markdown review. Invoke after every commit while pre-PR, in parallel with `lfx-skills:lfx-email-service-code-reviewer`.
- ▌ Committee Service Dev · linuxfoundation bundleRepo-local development conventions for the lfx-v2-committee-service. Auto-attaches on Go implementation paths (cmd/, internal/, pkg/, gen/), Goa design files under cmd/committee-api/design/, repo docs, the service-local Helm chart, Makefile, go.mod, and go.sum. Owns the generated-code boundary, slog logging via pkg/log, the pkg/errors domain-error family and its Goa mapping, request-context propagation through pkg/constants keys, NATS subject / KV / Object Store coding rules, committee-owned indexer and FGA contract docs, service chart wiring, table-driven tests with internal/infrastructure/mock fakes, gofmt and golangci-lint hygiene, and license headers. Central platform composition, V2 service classes, and cross-repo handoffs stay in lfx-skills:lfx-platform-architecture. Cross-repo topology and routing stay in lfx-skills:lfx. Committee-domain contracts (indexer-contract.md, fga-contract.md, invite-application-flows.md) are authoritative for what this service emits.
- ▌ Committee Service Preflight · linuxfoundationMechanical pre-PR validation for lfx-v2-committee-service. Checks working tree state, license headers, Go formatting, golangci-lint, API and CLI build, Go tests, repo-specific protected files, commit verification, and PR change summary. Run after /committee-service-pr-readiness has passed. Supports report-only or dry-run mode when requested.
- ▌ Committee Service Code Review · linuxfoundationHow to judge the implementation of an lfx-v2-committee-service pull request: the general quality dimensions (correctness, error handling, tests, concurrency, readability, code truthfulness), how to hold the diff to the repo's documented standards for this Goa + NATS Go service, and the security anchors that make a diff security-relevant here. Use on every PR that changes code, however small; this is the reviewer's line-level lens.
- ▌ Committee Service Pr Readiness · linuxfoundationPre-PR shape check for local lfx-v2-committee-service work. Audits branch name, JIRA reference, conventional commits, rebase status, DCO and GPG signing, total diff size, and repo-specific protected files against the target base branch. Does not audit Go code, generated output correctness, contracts, charts, or tests; run /committee-service-preflight after this shape check passes.
- ▌ Committee Service Code Reviewer · linuxfoundationRepo-owned reviewer skill `/committee-service-code-reviewer` for lfx-v2-committee-service, the `repo_code` reviewer loaded through the `/lfx-skills:lfx-local-review` lifecycle. Audits one pinned commit range — normally a commit against its first parent — against this repo's written rule surface — CLAUDE.md, the committee-service-dev skill and its Goa/NATS references, the committee-owned indexer/FGA/invite contract docs, the Heimdall RuleSet, and the Makefile. Every finding quotes a verbatim rule from a file in this repo; a rule that cannot be quoted is not a finding. Returns an ordinary Markdown review. Not a skill a developer invokes by hand.
- ▌ Committee Service Learnings Reviewer · linuxfoundationRepo-owned reviewer skill `/committee-service-learnings-reviewer` for lfx-v2-committee-service, the `repo_learnings` reviewer loaded through the `/lfx-skills:lfx-local-review` lifecycle. Matches one pinned commit range — normally a commit against its first parent — against the repo's canonical empirical knowledge base at `docs/reviews/knowledge-base/` — patterns extracted from real PR review threads on this repo, each carrying the reviewer thread, the developer's fixing commit, and current-code status. Every finding quotes a pattern entry; unsourced findings are dropped, and the known-false-positive floor is applied last, suppressing only where the pre-change base and the reviewed commit both cover the finding. Returns an ordinary Markdown review. Not a skill a developer invokes by hand.
- ▌ Speckit Plan · linuxfoundationExecute the implementation planning workflow using the plan template to generate design artifacts.
- ▌ Campaign Service Code Review · linuxfoundationHow to judge the implementation of an lfx-v2-campaign-service pull request: the Go quality dimensions (correctness, concurrency, error handling, tests, performance, readability, code truthfulness), how to hold the diff to the repo's documented standards, and the security anchors for a service that brokers to paid ad platforms and stores encrypted credentials. Use on every PR that changes code, however small; this is the reviewer's line-level lens.
- ▌ Campaign Service Code Reviewer · linuxfoundationRepo-owned code-review brain for lfx-v2-campaign-service, the code role of the local pre-PR reviewer trio. Audits the host-pinned commit range against this repository's written rule surface — CLAUDE.md, README, Makefile, docs/, the OKF knowledge bundle, the Goa design/gen boundary, Postgres migrations, platform-client conventions, dispatch contracts and the chart route/ruleset parity — and returns a Markdown review in which every finding quotes the rule it cites. Loaded directly by the launcher; not a skill a developer invokes by hand.
- ▌ Campaign Service Learnings Reviewer · linuxfoundationRepo-owned empirical review brain for lfx-v2-campaign-service, the learnings role of the local pre-PR reviewer trio. Matches the host-pinned commit range against the repo-owned knowledge base at docs/reviews/knowledge-base/ — patterns extracted from verified past PR review comments on this repo, each with a mechanical detect condition — and returns a Markdown review in which every finding quotes the pattern entry it matched. Applies the known-false-positive floor last, read at both the pre-change base and the target, suppressing a finding only when both floors would suppress it. Loaded directly by the launcher; not a skill a developer invokes by hand.
- ▌ Tinybird · linuxfoundationUpdate, deploy, or roll out a Tinybird pipe or datasource to staging or production. Use for "update a pipe", "push to Tinybird", "tb push", "tb pull", "change a datasource", "add a field to a pipe", or anything touching the `lfx_insights` / `lfx_insights_stg` Tinybird workspaces.
- ▌ Write Unit Tests · linuxfoundationWrite focused Vitest unit tests. Use when adding or improving unit tests for business logic, data access, common services, or other server modules.
- ▌ Write API E2e Tests · linuxfoundationWrite API end-to-end tests. Use when adding or changing API endpoints, or when the user asks for API e2e, smoke, or contract tests.
- ▌ Tb Quarantine Triage · linuxfoundation bundle<!-- Copyright The Linux Foundation and each contributor to LFX. -->
- ▌ Packages Worker Setup · linuxfoundationGet packages_worker running locally — first time or resuming after a break. Spins up packages-db if not running, applies any pending migrations, and starts the worker. All steps are safe to re-run. Use when: "set up packages worker", "start packages worker", "resume packages worker", "get packages-db running", "packages-db stopped", "restart the worker".
- ▌ Fix Vulns Git Integration · linuxfoundationAutomated vulnerability triage and dependency bumps for the git_integration worker (Python via uv + the two vendored Go modules). Fetches open Dependabot alerts scoped to git_integration manifests, correlates them with open Dependabot PRs, classifies each fix as safe or needs-human, validates safe fixes locally on the PR branches merged with latest main (uv sync / lint / pytest + full git-integration image build, which compiles both Go modules), updates safe PR branches server-side so they are one click from merge, then posts a "safe to merge" review summary to Slack and opens PRs for alerts Dependabot has no PR for. NEVER merges PRs, never dismisses alerts, never deploys without explicit user confirmation. Use when the user says "fix vulns", "bump deps", "dependabot triage", or asks about git_integration vulnerabilities.
- ▌ Scaffold Snowflake Connector · linuxfoundationUse when adding a new snowflake-connector data source to crowd.dev — a new platform or a new source within an existing platform that needs buildSourceQuery, transformer, activity types, migration, and all associated type registrations scaffolded.
- ▌ Packages Worker Add Entrypoint · linuxfoundationScaffold a new sub-worker inside packages_worker (npm, deps.dev, osv, scorecard, etc.) following the single-service multi-entry-point structure. Use when: "add a new packages worker", "scaffold a sub-worker in packages_worker", "new worker for packages-db", "add npm worker", "add OSV worker", "add deps.dev worker".
- ▌ Adr · linuxfoundationRecord an architecture decision as an ADR in api/docs/arch/adr/. Use when choosing between frameworks, libraries, databases, or architectural patterns; stating a decision with reasoning ("we decided X instead of Y because..."); or querying past decisions ("why did we choose X?").
- ▌ Commit · linuxfoundationGenerate a commit message and commit staged changes using git commit -s -S.
- ▌ Fix Vulns · linuxfoundationAutomated triage and fixing of Dependabot security vulnerabilities (IN-1189). Starts by asking which scope to tackle (critical, high, medium/low, or specific advisories) with checkboxes. Fetches open alerts, dedupes them, classifies each by origin (submodule vs local, dev-only vs runtime), then fans out one break-risk agent per package that must PROVE the update is safe for this codebase before any fix is applied. Applies safe fixes one at a time with incremental validation and ends with a report of what was fixed and what needs a human. Fixing only: NEVER runs git operations (no branch, commit, push, or PR) and produces no commit/PR drafts — reviewing and shipping the changes is entirely up to the user. Never dismisses alerts or auto-applies major version bumps. Use when the user says "fix vulns", "fix vulnerabilities", "dependabot alerts", "security audit fix", or invokes /fix-vulns.
- ▌ Review Pr · linuxfoundation bundleReview a pull request against Insights architecture standards — fetches PR diff, verifies previous comments are addressed, validates PR metadata (title, branch, JIRA, size), runs a code-standards check against every file in `.claude/rules/` and `.claude/hooks/guard-protected-files.sh`, and drafts inline review comments with suggested fixes. NEVER auto-posts comments or submits reviews — always presents a draft in the terminal for user approval before any comment lands on the PR. Use when reviewing PRs, checking PR quality, validating code changes, or when the user says "review", "check this PR", or "audit code".
- ▌
- ▌ Setup Docs · linuxfoundationRun the docs site, blog, or Storybook locally. Use when contributing to documentation, previewing blog posts, or developing UI components in isolation. Not needed for regular frontend development.
- ▌
- ▌ Member Service Dev · linuxfoundation bundlePath-scoped Go and Goa conventions for the lfx-v2-member-service repo. Auto-attaches when editing Go implementation, Goa design files, NATS KV cache code or request/reply handlers, logging, pagination, errors, request context, generated-code boundaries, tests, lint, formatting, or license headers. Inline guidance covers conventions every Go file in this repo follows, plus a Salesforce-integration callout. References cover repo-local NATS/KV contracts and the broader development workflow. Central platform composition stays in lfx-skills:lfx-platform-architecture; the membership endpoint workflow stays in the local member-add-endpoint skill.
- ▌ Member Add Endpoint · linuxfoundationUse when adding a new HTTP endpoint to the lfx-v2-member-service (b2b_org, b2b_org settings, project membership, key contacts, admin actions, or related membership resources). Covers the Goa design update, regeneration, handler implementation, test scaffolding, and the Heimdall ruleset update that authorization requires. Also use when modifying an existing endpoint's signature in a way that triggers a regen + ruleset update.
- ▌ Member Service Preflight · linuxfoundationMechanical pre-PR pipeline for lfx-v2-member-service. Runs the Go-specific working tree, license header, formatting, lint, build, tests, protected file, commit verification, and change-summary checks after /member-service-pr-readiness has passed. Supports default validation and report-only dry-run mode.
- ▌ Member Service Code Review · linuxfoundationHow to judge the implementation of an lfx-v2-member-service pull request: the grounding technique for reading a hunk in its real context, the general quality dimensions (correctness, error handling, logging, tests, concurrency, readability, code truthfulness), how to hold the diff to the repo's documented standards for this Goa + NATS + Salesforce Go service, the member-service specifics worth a second look, and the security anchors that make a diff security-relevant here. Use on every PR that changes code, however small; this is the reviewer's line-level lens.
- ▌ Member Service Pr Readiness · linuxfoundationShape-only pre-PR check for local lfx-v2-member-service work. Audits the branch name, LFXV2 ticket reference, conventional commit subjects, rebase status, DCO and GPG signing per commit, total diff size, and protected member-service files touched against the target base branch. Does not audit code behavior or run build/test/lint checks; run /member-service-preflight after this passes.
- ▌ Pr Conductor · linuxfoundationConduct an lfx-v2-newsletter-service pull request to a clean state: reconcile the AI reviewers' threads against the latest commits and developer replies, work with the engineer on findings that go against the architecture, and report whether the change is clean. Use when the task is to check whether AI-review findings are fixed or validly rebutted and to update the agentic gate. Posts one machine-readable agentic-check comment plus a summary of open blockers.
- ▌ Local Review Fallback · linuxfoundationLaunch the three local reviewers as Claude subagents when lfx-local-review selects the Claude fallback.
- ▌ Escalation Guidelines · linuxfoundationDetailed boundaries behind the needs-human decision for lfx-v2-newsletter-service: the critical surfaces (auth, the unauthenticated surface, schema, send behavior), shared and cross-repo contracts, scale-with-importance, and pipeline/supply-chain. Load this whenever judging whether a newsletter-service PR needs a human, as the detail behind the `needs-human-escalation` skill.
- ▌ Newsletter Service Dev · linuxfoundation bundleRepo-local Go coding conventions and implementation guidance for lfx-v2-newsletter-service. Auto-attaches when editing Go code, HTTP handlers, Postgres/Bun repository code, embedded schema, NATS upstream clients, recipient resolution, email fan-out, newsletter API DTOs, Makefile, Helm chart templates, or service-owned docs. Owns the newsletter HTTP API, draft/send state transitions, email dispatch, unsubscribe, local analytics/open tracking, recipient resolution, tests, formatting, linting, and license headers. Central platform composition stays in lfx-skills:lfx-platform-architecture; cross-repo routing stays in lfx-skills:lfx.
- ▌ Agentic Comment Format · linuxfoundationThe exact format for the two verdict comments the agentic review posts on a lfx-v2-newsletter-service pull request: the needs-human verdict (escalation) and the agentic-check verdict (conductor). Use whenever you post either verdict. Defines the human presentation and the machine-readable markers that the deterministic apply step parses, so writer and reader stay in sync.
- ▌ Needs Human Escalation · linuxfoundationDecide whether an lfx-v2-newsletter-service pull request needs a human's sign-off before it can merge (the needs-human gate), regardless of code quality. Use when the task is the needs-human escalation on a PR. Posts a single machine-readable needs-human verdict comment via add_issue_comment.
- ▌ Newsletter Code Review · linuxfoundationHow to judge the implementation of an lfx-v2-newsletter-service pull request: the general quality dimensions (correctness, error handling, tests, performance, readability, code truthfulness) and how to hold the diff to the repo's documented standards. Use on every PR that changes code, however small; this is the reviewer's line-level lens. Security has its own skill (newsletter-security-review).
- ▌ Newsletter Security Review · linuxfoundationSecurity review for lfx-v2-newsletter-service pull requests. Use when a PR touches a handler, auth, persistence, the dispatch path, recipient data, config, or the chart. Applies a diff-aware, high-confidence, low-false-positive methodology (adapted from Anthropic's claude-code-security-review) to this service's durable threat anchors: recipient PII, the deliberately unauthenticated endpoints, JWT verification, gateway-delegated authorization, SQL construction, and secrets. Discovers the concrete guards from the code at review time; this skill carries the method, not an inventory.
- ▌ Newsletter Service Preflight · linuxfoundationRepo-local Go mechanical pre-PR pipeline for lfx-v2-newsletter-service. Checks working tree status, license headers, Go formatting, lint/vet, build, tests, protected newsletter-service files, commit verification, and PR change summary. Run after /newsletter-service-pr-readiness. Supports report-only or dry-run mode when the contributor does not want file mutations.
- ▌ Newsletter Service Agentic Pr · linuxfoundationHow to drive an open lfx-v2-newsletter-service pull request through the agentic review flow: read the lfx-reviewer "Agentic review check" comment, fix or rebut every blocking finding, answer every review thread, push one batched round at a time, and loop until the check is green on the current head with every thread answered — then report the ending: needs-human review before merge, or clear for the gate/automerge path. Use whenever a PR is open on this repo and the work involves review iteration — responding to Copilot or conductor findings, checking why `agentic-review/clean` is failing or why the gate has not approved, handling the `needs-human` label, or pushing fixes to an open PR. This is the PR driver's operating manual: the driver is a worktree-isolated background agent that works the PR autonomously (fixes, rebuttals, replies, pushes). The main session only launches the driver right after opening any PR here — with a minimal prompt pointing at this skill — and relays its round notes.
- ▌ Newsletter Service Cut Release · linuxfoundationCut a new GitHub release/tag for lfx-v2-newsletter-service from main, verify the tagged build published the image and Helm chart, then open a version-bump PR on lfx-v2-argocd pinning the target environments to the new version. Use when the user asks to "cut a release", "release a new version", or "bump the newsletter service in argocd".
- ▌ Newsletter Service Pr Readiness · linuxfoundationRepo-local pre-PR shape check for lfx-v2-newsletter-service. Audits branch name, JIRA reference, conventional commits, rebase status, DCO + GPG signing on every commit, total diff size, and protected newsletter-service files touched against the selected base branch. Shape check only: does not review Go code, run tests, format files, lint, build, or create a PR.
- ▌ Newsletter Service Code Reviewer · linuxfoundationRepo-owned code-review brain for local pre-PR review on lfx-v2-newsletter-service. Audits the reviewed change against this repo's written rule surface — CLAUDE.md, the repo-local skills, and the service-owned contract docs — and returns an ordinary Markdown review in which every finding quotes a repo rule verbatim. Loaded directly by the `lfx-local-review` launcher through the `local-code-review` discovery alias; not a skill a developer invokes by hand.
- ▌ Newsletter Service Learnings Reviewer · linuxfoundationRepo-owned learnings review brain for local pre-PR review on lfx-v2-newsletter-service. Matches the reviewed change against the empirical pattern knowledge base in docs/reviews/knowledge-base/ — patterns extracted from real past PR review comments on this repo — and returns an ordinary Markdown review in which every finding quotes a KB pattern entry. Loaded directly by the `lfx-local-review` launcher through the `local-learnings-review` discovery alias; not a skill a developer invokes by hand.
- ▌ Dco · linuxfoundationRecover from missing DCO sign-off on commits. Handles the single-commit amend, older-commit recovery via interactive rebase or cherry-pick, and explains the Probot DCO check that blocks PRs without sign-off. Use when a PR fails the DCO check, when a commit needs a Signed-off-by trailer added retroactively, or when sign-off was forgotten during rebase / cherry-pick / amend.
- ▌ Nats · linuxfoundationUse when publishing or subscribing to NATS from the Self Serve Express BFF — touching `nats.service.ts`, sending NATS requests, consuming subjects, or troubleshooting NATS connectivity. Trigger phrases include "NATS publish", "NATS subscribe", "NATS request", "nats.service", "project RPC", "inter-service messaging".
- ▌ Setup · linuxfoundation bundleEnvironment setup from zero — prerequisites, clone, install, env vars via 1Password, and dev server. Use for getting started, first-time setup, broken environments, install failures, or missing env vars.
- ▌ Drawer · linuxfoundationUse when building or modifying a Self Serve drawer component — slide-in detail panels with lazy data loading, chart integration, two-way `[(visible)]` bindings, and the standard responsive width class chain. Trigger phrases include "building a drawer", "open in a drawer", "drawer component", "lazy-load on open", "side panel".
- ▌ Preflight · linuxfoundation bundleMechanical pre-PR pipeline, license headers, format, lint, build, protected file check, commit verification, and PR change summary. Run as the final deterministic check inside Mode 2 of `CLAUDE.md`'s **Pre-PR review** section, after the preceding review, fix, documentation-currency, and commit work and after `/lfx-self-serve-pr-readiness`. Review protocol and pattern/convention auditing are not owned by this skill.
- ▌ Snowflake · linuxfoundationUse when writing or modifying Self Serve Snowflake queries, touching `snowflake.service.ts`, or building analytics endpoints that hit the singleton Snowflake pool. Trigger phrases include "Snowflake query", "analytics endpoint", "snowflake.service", "SQL bind", "warehouse", "snowflake pool", "direct SQL".
- ▌ Pagination · linuxfoundationUse when a Self Serve backend endpoint returns lists, when you need cursor pagination (`page_token` / `page_size`) against the query service, or when fetching all pages of a resource via the `fetchAllQueryResources` helper. Trigger phrases include "paginated endpoint", "page_token", "page_size", "infinite scroll backend", "list endpoint", "fetch all pages".
- ▌ Lens Persona · linuxfoundationUse when touching Self Serve dashboards, persona behavior, lens switching, `LensService`, `ProjectContextService`, or any code that varies behavior by user persona (Contributor, Maintainer, ED, Board Member, Admin Mode). Trigger phrases include "lens", "persona", "ED mode", "Admin Mode", "PCC", "dashboard variant".
- ▌ Lfx Review Pr · linuxfoundationReview a pull request against LFX architecture standards. Requires the reviewer's HEAD to be the PR's branch (author scenarios are natural; external reviewers run `gh pr checkout <N>` first). Fetches main fresh, then launches `lfx-skills:lfx-general-code-reviewer` and `lfx-skills:lfx-self-serve-code-reviewer` in full-branch mode. The subagents audit the PR branch's diff against `origin/main` and render markdown reports covering general code review, upstream API contracts, and repo conventions (rules, checklists, architecture). This skill body adds what only a post-PR skill can do: verifying prior review comments are addressed, walking the PR-shape checklist (branch/ ticket-ref(JIRA or GH issue)/commits/DCO+GPG/rebase/diff-size/protected-files/PR-title/external-refs), applying new-contributor educational tone, presenting a draft for explicit approval, and posting via /review only after user go-ahead. NEVER auto-posts comments or submits reviews. Use when reviewing PRs, checking PR quality, validating code chan
- ▌ Self Serve Dev · linuxfoundation bundleGuided development workflow for building, fixing, updating, or refactoring code, components, services, backend endpoints, shared types, or full features. Use whenever someone wants to add a feature, fix a bug, modify existing code, create something new, refactor, or implement any code change.
- ▌ Self Serve Code Review · linuxfoundationHow to judge the implementation of an lfx-self-serve (LFX One) pull request: the general quality dimensions (correctness, error handling, tests, performance, readability, code truthfulness) and how to hold the diff to the repo's documented standards for the Angular SSR app and the Express BFF. Use on every PR that changes code, however small; this is the reviewer's line-level lens. Security has its own skill (self-serve-security-review).
- ▌ Lfx Self Serve Code Review · linuxfoundationPost-commit code-convention audit for lfx-self-serve. Audits the latest commit in the lfx-self-serve repo against the repo documented rule surface: `.claude/rules/`, the four `docs/reviews/` checklists, architecture docs, and upstream API contracts. May be launched from the LFX workspace root, but always operates in `lfx-self-serve`. Every repo-convention finding quotes a loaded source. Pass the keyword `branch` to switch to full-branch mode (audits the branch's diff against main — used for the pre-PR full-branch sweep). Renders a markdown review with Upstream API / data-layer validation and Repo conventions sections. Invoke after every commit while pre-PR, in parallel with `lfx-skills:lfx-general-code-review` and `lfx-self-serve-learnings-review`.
- ▌ Self Serve Security Review · linuxfoundationSecurity review for lfx-self-serve (LFX One) pull requests. Use when a PR touches the auth middleware or route classification, the OIDC session or token-exchange paths, a server controller or service, a proxy call to an upstream microservice, the public surface, user identity, impersonation or persona-based authorization, PII or logging, URL handling or redirects, anything rendered with `[innerHTML]`, or what crosses the SSR-to-client boundary. Applies a diff-aware, high-confidence, low-false-positive methodology (adapted from Anthropic's claude-code-security-review) to this application's durable threat anchors. Discovers the concrete guards from the code at review time; this skill carries the method, not an inventory.
- ▌ Lfx Self Serve Pr Readiness · linuxfoundation bundlePre-PR shape check on local lfx-self-serve work. Audits PR-shape sanity (branch name, ticket reference — JIRA or GitHub Issue —, conventional-commit format, rebase status, DCO + GPG signing per commit, total diff size, and protected files touched) against the target base branch. Does NOT audit code; the review protocol is owned by `CLAUDE.md`'s **Pre-PR review** section. Run inside Mode 2, once its whole-branch review, the required finding fixes, the documentation-currency updates, and the resulting signed/DCO commit are complete.
- ▌ Lfx Self Serve Learnings Review · linuxfoundationPost-commit empirical-pattern review for lfx-self-serve. Audits the latest commit in the lfx-self-serve repo against `docs/reviews/knowledge-base/` — patterns extracted from past PR review comments on this repo. May be launched from the LFX workspace root, but always operates in `lfx-self-serve`. Findings are gated by KB matches: every finding must quote a pattern entry; unsourced findings are dropped. Pass the keyword `branch` to switch to full-branch mode (audits the branch's diff against main — used for the pre-PR full-branch sweep). Renders a markdown review. Invoke after every commit while pre-PR, in parallel with `lfx-self-serve-code-review`.
- ▌ Lfx · linuxfoundation bundleLFX cross-repo topology and ownership router. Use when the task spans more than one LFX repo, asks "which repo owns X", "where does Y live", "what repos does this touch", "what consumes Z", or needs a peer-repo file path from inside a single repo. Loads per-repo configs when invoked from the LFX workspace root with a full task prompt; gives targeted cross-repo guidance when invoked from inside a single repo. Also answers LFX glossary and topology questions, and performs read-only discovery when the user asks whether a contract, API, event, field, workflow, or repo capability exists. Do not fire for single-repo implementation tasks where the active repo's own CLAUDE.md already governs (those belong to the repo's local skills). Do not fire for V2 platform composition, service classes, or cross-service handoffs (use `/lfx-skills:lfx-platform-architecture`), ITX wrapper plumbing (`/lfx-skills:lfx-itx-integration`), or Intercom app/Fin workflows (`/lfx-skills:lfx-intercom`).
- ▌ Lfx Setup · linuxfoundationEnvironment setup for any LFX repo, prerequisites, clone, install, env vars, and dev server. Adapts to repo type (Angular or Go). Use for getting started, first-time setup, broken environments, or install failures.
- ▌ Lfx Intercom · linuxfoundation bundleEverything Intercom for LFX — Angular app integration (code) and Fin AI optimization (support/CX). Use this skill for: adding or fixing Intercom in an LFX Angular app, auditing integrations against the LFX canonical pattern, correcting missing JWT pre-set, broken shutdown, missing Auth0 claim, wrong app IDs, or absent CSP entries — AND for Fin Guidance writing, Help Center optimization, resolution rate improvement, Fin escalation patterns, Copilot tips, Topics Explorer, Fin Attributes, daily review rituals, and Fin best practices. Routes to the right section based on context. Trigger on: any Intercom question, "Fin tips", "improve Fin", "Fin guidance", "Fin resolution rate", "Help Center optimization", "Copilot tips", "Angular Intercom", "IntercomService", "JWT Intercom", "Fin re-engagement", "Fin handoff", or any Intercom-related support or development question.
- ▌ Lfx Git Setup · linuxfoundation bundleInteractive setup guide for LFX contributors to configure Git for DCO signoff and GPG-signed commits. Use this skill whenever someone asks about setting up Git signing, DCO signoff, GPG keys for commits, configuring `~/.gitconfig` for signing, adding a GPG key to GitHub, or any variation of "how do I sign my commits?". Also trigger it when a user says their commits aren't showing as "Verified" on GitHub, when they're onboarding to an LFX project and need to meet contribution requirements, or when they ask about `git commit -s`, `--signoff`, `Signed-off-by`, or `commit.gpgSign`. This skill works for technical and non-technical users alike.
- ▌ Lfx Pr Catchup · linuxfoundationMorning PR catch-up dashboard, shows unresolved comments, status changes, stale PRs, and approved-but-not-merged PRs across all your open PRs.
- ▌ Lfx Pr Resolve · linuxfoundation bundleAddress PR review comments, fetches unresolved threads, makes code changes, commits with a summary, responds to each comment, resolves threads, posts a follow-up summary, dismisses stale "changes requested" reviews, and re-requests review. Use whenever someone wants to address PR feedback, fix review comments, resolve PR threads, or iterate on a pull request after review.
- ▌ Lfx Local Review · linuxfoundation bundleRun the local pre-PR review trio on the current repo — the general reviewer plus the repo's own code and learnings reviewers — on headless Pi when it is available, or Claude subagents otherwise, and return their ordinary Markdown reports. Use after a commit, in a repo that owns local review skills. Author-side only; reviewers may read GitHub but never write PR, gate or merge state.
- ▌ Lfx Test Journey · linuxfoundation bundleCombine multiple feature branches across repos into worktrees for end-to-end journey testing. Create, refresh, and teardown integration environments that merge branches from multiple repos.
- ▌ Lfx Data Engineer · linuxfoundation bundleGuide non-dbt developers through building PR-ready data models, tests, and transformations in the lf-dbt repo. Encodes the medallion architecture (bronze/silver/gold/platinum), Snowflake SQL conventions, sqlfluff formatting, dbt testing patterns, key macros, and data governance rules. Use this skill any time someone asks about writing dbt models, adding data tests, creating SQL transformations, fixing pipeline failures, or contributing to the lf-dbt repository.
- ▌ Lfx Itx Integration · linuxfoundationCentral explainer for how LFX V2 wrapper services integrate with ITX (the Linux Foundation IT backend) and with the legacy v1 system. Covers OAuth2 M2M to ITX via private key JWT assertion, v2 UUID to v1 Salesforce ID mapping via the NATS request/reply subject `lfx.lookup_v1_mapping`, v1 to v2 event sync via NATS JetStream KV bucket watchers, and the canonical `ITX_*` environment variable contract. Fires on prompts like "ITX", "OAuth2 M2M to ITX", "ID mapping v1 v2", "Salesforce SFID mapping", "v1 KV event sync", "lfx.lookup_v1_mapping", "ITX_CLIENT_ID", "ITX_CLIENT_PRIVATE_KEY", "ITX_AUDIENCE", "ITX_BASE_URL", "JetStream KV watcher", "v1 to v2 sync", "wrapper service ITX", "private key JWT assertion", "id mapper", "v1-objects bucket", "EVENT_STREAM_NAME", "EVENT_CONSUMER_NAME". Read-only; routes implementation work to the owning wrapper repo.
- ▌ Lfx Object Store Ops · linuxfoundationProvisioning requirements for LFX object storage backends in deployed environments (prod, staging, shared dev): private S3 buckets, CloudFront with Origin Access Control, shared wildcard certificate, and IRSA write access, all in `lfx-v2-opentofu`. Written for the linuxfoundation GitHub org's ops audience — see the `-ops` skill convention in `/lfx-skills:lfx`. Fires on prompts like "provision a bucket", "object storage backend", "CloudFront for uploads", "S3 bucket opentofu", "IRSA for S3", "object store CDN", "bucket policy", "wildcard cert uploads". Requirements only; the implementing agent owns the HCL.
- ▌ Lfx Snowflake Access · linuxfoundationGuide users through requesting Snowflake access at the Linux Foundation. Handles two request types: (1) individual user access, adding or modifying an entry in users.tf in the lfx-snowflake-terraform repo, and (2) service account creation, adding an entry in service_accounts.tf. For each, the skill collects the necessary details, generates the exact Terraform HCL block to add, explains where to place it, and guides the user through the PR process. Use this skill any time someone asks about Snowflake access, permissions, user provisioning, service accounts, or making changes to the lfx-snowflake-terraform repo, including phrases like "get access to Snowflake", "add me to Snowflake", "need a service account", "request Snowflake permissions", "I need to query Snowflake", or "how do I get Snowflake access".
- ▌ Lfx V2 Ticket Writer · linuxfoundationCreate a new ticket in the LFXV2 Jira project (linuxfoundation.atlassian.net). Guides the user through picking an issue type (Bug, Story, Task, Epic), writing a concise summary, and capturing the requirement, feature, or bug context, collecting reproduction steps for bugs. Optionally attaches a parent epic, labels, or priority if the user provides them. Submits the ticket via Atlassian MCP and returns the URL. Use this skill any time someone asks to "create a Jira ticket", "open an LFXV2 ticket", "file a bug", "log a story", "write up a feature request", "draft a ticket", or any variation of submitting work into LFXV2.
- ▌ Lfx General Code Review · linuxfoundationThe general code-review method for LFX local reviews — correctness, security, data privacy, error handling, simplicity, naming, DRY, testing, performance and style, over one explicit pinned range, normally the single commit at the branch's tip. Carries no repo-specific rulebook. Loaded by the lfx-local-review host in either harness, headless Pi or a generic Claude subagent. Returns an ordinary Markdown review.
- ▌ Lfx Object Store Design · linuxfoundationCentral explainer for adding object storage capability to an LFX V2 service. Covers the S3-compatible storage decision, hard requirements (no presigned uploads, private buckets only, 20 MB cap, per-service bucket ownership, metadata/payload separation), Go AWS SDK v2 code patterns, the singleton and collection API shapes, the Helm chart credential-mode contract (static creds for local, IRSA for deployed), the nats-s3 sidecar local backend, the nginx-s3-gateway local CDN model, and the S3_BUCKET/AWS_REGION/S3_ENDPOINT_URL/S3_CREATE_MISSING_BUCKET/ CDN_URL_PREFIX env var contract. Fires on prompts like "object storage", "S3", "file upload", "upload endpoint", "attachments", "logo upload", "bucket", "nats-s3", "nginx-s3-gateway", "CDN_URL_PREFIX", "presigned URL", "PutObject", "IRSA S3", "S3_ENDPOINT_URL", "public_url", "download endpoint", "multipart upload". Read-only; routes implementation work to the owning service repo and provisioning to `/lfx-skills:lfx-object-store-ops`.
- ▌ Lfx Platform Architecture · linuxfoundationCentral explainer for how the LFX V2 platform components compose: Self Serve, Goa services, NATS, JetStream KV, fga-sync, OpenFGA, indexer-service, OpenSearch, query-service, access-check, Heimdall, Gateway API, Auth0, Helm, and ArgoCD. Use when tracing platform write, read, access-check, authorization, indexing, deployment, service-classification, or cross-repo ownership flows. Fires on prompts like "how does FGA flow", "where does the indexer fit", "what's the platform shape", "native service", "wrapper service", "new V2 service", "Heimdall vs FGA", "what owns the OpenFGA model", "how does query-service read resources", "how does access-check work", "which repo owns deployed values", or "which service consumes index messages". Do not use for V2 Go service coding conventions; the owning repo's path-scoped `<short-repo-name>-dev` skill should attach after routing.
- ▌ Lfx Cdp Snowflake Connectors · linuxfoundationUse when adding a new snowflake-connector data source to crowd.dev — a new platform or a new source within an existing platform that needs buildSourceQuery, transformer, activity types, migration, and all associated type registrations scaffolded.
- ▌ Copilot Code Reviewer · linuxfoundationSenior review method for lfx-skills pull requests. Use whenever the task is to review a pull request on this repo, whatever it changes.
- ▌ Lfx Skills Code Review · linuxfoundationHow to judge an lfx-skills pull request: what makes a skill or reviewer agent sound (frontmatter, triggers, internal consistency, reference accuracy) and whether the change respects the central-vs-repo boundary of the LFX skills fanout architecture. Use on every pull request this repo receives; this is the reviewer's repo-specific lens.