all publishers

linuxfoundation

@linuxfoundation source repo

110 published skills · page 1 of 2

  1. ▌
    Preflight 3 · linuxfoundation
    Pre-PR validation — license headers, format, lint, TypeScript check, build, and protected file check. Use before submitting any PR, to check if code is ready, validate changes, or verify a branch before review.
    17 repo stars
  2. ▌
    Copilot Code Reviewer 3 · linuxfoundation
    Senior code-review method for lfx-v2-meeting-service pull requests. Use when the task is to review a PR for correctness, design, and security on this repo.
    17 repo stars
  3. ▌
    Setup 2 · linuxfoundation
    Full development environment setup from scratch — prerequisites, dependencies, .env file, optional local PostgreSQL database (for auth/collections/chat work), and dev server. Use for first-time setup, broken environments, missing env vars, or when the app won't start.
    17 repo stars
  4. ▌
    Local Review Fallback 2 · linuxfoundation
    Launch the three local reviewers as Claude subagents when lfx-local-review selects the Claude fallback.
    17 repo stars
  5. ▌
    Adr 2 · linuxfoundation
    Record an architecture decision as an ADR in docs/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?").
    17 repo stars
  6. ▌
    Commit 2 · linuxfoundation
    Generate a commit message and commit staged changes using git commit -s -S.
    17 repo stars
  7. ▌
    Preflight 2 · linuxfoundation
    Pre-PR validation — working tree status, format, lint, TypeScript check, and protected file check. Workspace-aware: detects which of backend/, frontend/, services/apps/*, services/libs/* were changed and runs only the relevant scripts. Use before submitting any PR, to check if code is ready, or to validate a branch before review.
    17 repo stars
  8. ▌
    Review Pr 2 · linuxfoundation bundle
    Review a pull request against CDP architecture standards — fetches PR diff, verifies previous comments are addressed, validates PR metadata (title, branch, JIRA key, size), runs a code-standards enforcer 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".
    17 repo stars
  9. ▌
    Pr Conductor 2 · linuxfoundation
    Conduct an lfx-v2-member-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.
    17 repo stars
  10. ▌
    Copilot Code Reviewer 2 · linuxfoundation
    Senior code-review method for lfx-v2-member-service pull requests: reviewer scope and knowledge sources, how to place a change in this Salesforce-backed Go service and in the LFX V2 platform around it, and the signal discipline that keeps review quiet unless it has something real. Use when the task is to review a PR on this repo for correctness, design, or security, including on a re-review after a new push. Posts inline severity-tagged comments plus a summary on the PR itself.
    17 repo stars
  11. ▌
    Escalation Guidelines 2 · linuxfoundation
    Detailed boundaries behind the needs-human decision for lfx-v2-member-service: authentication and the Heimdall RuleSet, the access grants this service emits, writes to production Salesforce data and the shared API budget, authoritative no-TTL state, cross-repo contracts, integrations and secrets, infra and supply chain, and scale-with-importance. Load this whenever judging whether an lfx-v2-member-service PR needs a human, as the detail behind the `needs-human-escalation` skill.
    17 repo stars
  12. ▌
    Agentic Comment Format 2 · linuxfoundation
    The exact format for the two verdict comments the agentic review posts on a lfx-v2-member-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.
    17 repo stars
  13. ▌
    Needs Human Escalation 2 · linuxfoundation
    Decide whether an lfx-v2-member-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.
    17 repo stars
  14. ▌
    Dco 2 · linuxfoundation
    Recover 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.
    17 repo stars
  15. ▌
    Speckit Tasks 2 · linuxfoundation
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    17 repo stars
  16. ▌
    Speckit Specify 2 · linuxfoundation
    Create or update the feature specification from a natural language feature description.
    17 repo stars
  17. ▌
    Speckit Tasks · linuxfoundation
    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    17 repo stars
  18. ▌
    Speckit Specify · linuxfoundation
    Create or update the feature specification from a natural language feature description.
    17 repo stars
  19. ▌
    Vue · linuxfoundation bundle
    Use 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
    17 repo stars
  20. ▌
    Nuxt · linuxfoundation bundle
    Use 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+.
    17 repo stars
  21. ▌
    Uikit · linuxfoundation bundle
    Use 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
    17 repo stars
  22. ▌
    Populate Jtbds · linuxfoundation
    Populate @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.
    17 repo stars
  23. ▌
    Helm Local Stack · linuxfoundation
    Use 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".
    17 repo stars
  24. ▌
    Render Permissions · linuxfoundation
    Render 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.
    17 repo stars
  25. ▌
    Meeting Service Code Review · linuxfoundation
    How 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.
    17 repo stars
  26. ▌
    Meeting Service Code Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  27. ▌
    Meeting Service Learnings Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  28. ▌
    Email Service Dev · linuxfoundation bundle
    Repo-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.
    17 repo stars
  29. ▌
    Email Service Preflight · linuxfoundation
    Repo-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.
    17 repo stars
  30. ▌
    Email Service Pr Readiness · linuxfoundation
    Repo-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.
    17 repo stars
  31. ▌
    Email Service Code Reviewer · linuxfoundation
    Post-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.
    17 repo stars
  32. ▌
    Email Service Learnings Reviewer · linuxfoundation
    Post-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`.
    17 repo stars
  33. ▌
    Committee Service Dev · linuxfoundation bundle
    Repo-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.
    17 repo stars
  34. ▌
    Committee Service Preflight · linuxfoundation
    Mechanical 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.
    17 repo stars
  35. ▌
    Committee Service Code Review · linuxfoundation
    How 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.
    17 repo stars
  36. ▌
    Committee Service Pr Readiness · linuxfoundation
    Pre-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.
    17 repo stars
  37. ▌
    Committee Service Code Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  38. ▌
    Committee Service Learnings Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  39. ▌
    Speckit Plan · linuxfoundation
    Execute the implementation planning workflow using the plan template to generate design artifacts.
    17 repo stars
  40. ▌
    Campaign Service Code Review · linuxfoundation
    How 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.
    17 repo stars
  41. ▌
    Campaign Service Code Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  42. ▌
    Campaign Service Learnings Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  43. ▌
    Tinybird · linuxfoundation
    Update, 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.
    17 repo stars
  44. ▌
    Write Unit Tests · linuxfoundation
    Write focused Vitest unit tests. Use when adding or improving unit tests for business logic, data access, common services, or other server modules.
    17 repo stars
  45. ▌
    Write API E2e Tests · linuxfoundation
    Write API end-to-end tests. Use when adding or changing API endpoints, or when the user asks for API e2e, smoke, or contract tests.
    17 repo stars
  46. ▌
    Tb Quarantine Triage · linuxfoundation bundle
    <!-- Copyright The Linux Foundation and each contributor to LFX. -->
    17 repo stars
  47. ▌
    Packages Worker Setup · linuxfoundation
    Get 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".
    17 repo stars
  48. ▌
    Fix Vulns Git Integration · linuxfoundation
    Automated 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.
    17 repo stars
  49. ▌
    Scaffold Snowflake Connector · linuxfoundation
    Use 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.
    17 repo stars
  50. ▌
    Packages Worker Add Entrypoint · linuxfoundation
    Scaffold 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".
    17 repo stars
  51. ▌
    Adr · linuxfoundation
    Record 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?").
    17 repo stars
  52. ▌
    Commit · linuxfoundation
    Generate a commit message and commit staged changes using git commit -s -S.
    17 repo stars
  53. ▌
    Fix Vulns · linuxfoundation
    Automated 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.
    17 repo stars
  54. ▌
    Review Pr · linuxfoundation bundle
    Review 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".
    17 repo stars
  55. ▌
    DB Migrate · linuxfoundation bundle
    DB Migrate
    17 repo stars
  56. ▌
    Setup Docs · linuxfoundation
    Run 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.
    17 repo stars
  57. ▌
    Tech Writer · linuxfoundation bundle
    Tech Writer
    17 repo stars
  58. ▌
    Member Service Dev · linuxfoundation bundle
    Path-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.
    17 repo stars
  59. ▌
    Member Add Endpoint · linuxfoundation
    Use 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.
    17 repo stars
  60. ▌
    Member Service Preflight · linuxfoundation
    Mechanical 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.
    17 repo stars
  61. ▌
    Member Service Code Review · linuxfoundation
    How 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.
    17 repo stars
  62. ▌
    Member Service Pr Readiness · linuxfoundation
    Shape-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.
    17 repo stars
  63. ▌
    Pr Conductor · linuxfoundation
    Conduct 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.
    17 repo stars
  64. ▌
    Local Review Fallback · linuxfoundation
    Launch the three local reviewers as Claude subagents when lfx-local-review selects the Claude fallback.
    17 repo stars
  65. ▌
    Escalation Guidelines · linuxfoundation
    Detailed 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.
    17 repo stars
  66. ▌
    Newsletter Service Dev · linuxfoundation bundle
    Repo-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.
    17 repo stars
  67. ▌
    Agentic Comment Format · linuxfoundation
    The 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.
    17 repo stars
  68. ▌
    Needs Human Escalation · linuxfoundation
    Decide 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.
    17 repo stars
  69. ▌
    Newsletter Code Review · linuxfoundation
    How 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).
    17 repo stars
  70. ▌
    Newsletter Security Review · linuxfoundation
    Security 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.
    17 repo stars
  71. ▌
    Newsletter Service Preflight · linuxfoundation
    Repo-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.
    17 repo stars
  72. ▌
    Newsletter Service Agentic Pr · linuxfoundation
    How 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.
    17 repo stars
  73. ▌
    Newsletter Service Cut Release · linuxfoundation
    Cut 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".
    17 repo stars
  74. ▌
    Newsletter Service Pr Readiness · linuxfoundation
    Repo-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.
    17 repo stars
  75. ▌
    Newsletter Service Code Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  76. ▌
    Newsletter Service Learnings Reviewer · linuxfoundation
    Repo-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.
    17 repo stars
  77. ▌
    Dco · linuxfoundation
    Recover 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.
    17 repo stars
  78. ▌
    Nats · linuxfoundation
    Use 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".
    17 repo stars
  79. ▌
    Setup · linuxfoundation bundle
    Environment 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.
    17 repo stars
  80. ▌
    Drawer · linuxfoundation
    Use 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".
    17 repo stars
  81. ▌
    Preflight · linuxfoundation bundle
    Mechanical 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.
    17 repo stars
  82. ▌
    Snowflake · linuxfoundation
    Use 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".
    17 repo stars
  83. ▌
    Pagination · linuxfoundation
    Use 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".
    17 repo stars
  84. ▌
    Lens Persona · linuxfoundation
    Use 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".
    17 repo stars
  85. ▌
    Lfx Review Pr · linuxfoundation
    Review 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
    17 repo stars
  86. ▌
    Self Serve Dev · linuxfoundation bundle
    Guided 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.
    17 repo stars
  87. ▌
    Self Serve Code Review · linuxfoundation
    How 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).
    17 repo stars
  88. ▌
    Lfx Self Serve Code Review · linuxfoundation
    Post-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`.
    17 repo stars
  89. ▌
    Self Serve Security Review · linuxfoundation
    Security 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.
    17 repo stars
  90. ▌
    Lfx Self Serve Pr Readiness · linuxfoundation bundle
    Pre-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.
    17 repo stars
  91. ▌
    Lfx Self Serve Learnings Review · linuxfoundation
    Post-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`.
    17 repo stars
  92. ▌
    Lfx · linuxfoundation bundle
    LFX 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`).
    17 repo stars
  93. ▌
    Lfx Setup · linuxfoundation
    Environment 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.
    17 repo stars
  94. ▌
    Lfx Intercom · linuxfoundation bundle
    Everything 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.
    17 repo stars
  95. ▌
    Lfx Git Setup · linuxfoundation bundle
    Interactive 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.
    17 repo stars
  96. ▌
    Lfx Pr Catchup · linuxfoundation
    Morning PR catch-up dashboard, shows unresolved comments, status changes, stale PRs, and approved-but-not-merged PRs across all your open PRs.
    17 repo stars
  97. ▌
    Lfx Pr Resolve · linuxfoundation bundle
    Address 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.
    17 repo stars
  98. ▌
    Lfx Local Review · linuxfoundation bundle
    Run 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.
    17 repo stars
  99. ▌
    Lfx Test Journey · linuxfoundation bundle
    Combine 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.
    17 repo stars
  100. ▌
    Lfx Data Engineer · linuxfoundation bundle
    Guide 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.
    17 repo stars