Agent skill · software engineering · jeremylongshore
palantir-ci-integration
Design and verify Foundry-native continuous-integration and review gates for Code Repositories and transforms. Use when a team needs branch checks, unit tests, dataset-impact review, or controlled promotion. Trigger with "Palantir CI" or "Foundry repository checks".
Why this skill is useful
Adds a complete CI/CD pipeline configuration for Palantir Foundry integrations with GitHub Actions, including custom linting scripts and environment variable management.
What it needs
Requires gh installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Palantir Foundry CI and Review Gates Overview Build the quality gate around Foundry Code Repository branches, automatic checks, unit tests, and pull-request review. External Git hosting may mirror evidence, but it must not replace the checks that Foundry runs against repository inputs, outputs, dependencies, and platform builds. Prerequisites Identify the Foundry enrollment, Code Repository, target branch, owned datasets, and release owner. Confirm whether the repository uses Python transforms, TypeScript, or another supported project type. Read references/official-docs.md and inspect the repository's effective CI and branch settings before proposing changes. Use a sandbox branch and non-production data until the checks and rollback path are proven. Current Contract A commit to a Code Repository branch runs automatic checks; the Checks tab is the primary result surface. Python unit tests can participate in repository CI when configured according to the repository's supported build layout. Transform input and output declarations are evaluated by CI and cannot be chosen dynamically at build time. A pull request can require approving review before merge, and reviewers can inspect dataset impact for transform changes. Instructions 1. Inventory current branch protection, checks, unit-test wiring, build ownership, and required reviewers. 2. Create or update tests so each test isolates one unit of transform logic and avoids live external dependencies. 3. Run the Foundry branch checks and preserve the exact failing check, build report, and dependency evidence. 4. Open a Foundry pull request, review code plus dataset impact, and obtain the required independent approval. 5. Merge only the exact reviewed commit, then verify the main-branch checks and downstream build behavior. Tool Discipline Use Glob to locate candidate repositories, manifests, configurations, and evidence without widening scope. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-ci-integration