palantir-ci-integration
Configure CI/CD pipelines for Palantir Foundry integrations with GitHub Actions. Use when setting up automated testing, running transforms validation, or integrating Foundry SDK tests into your build process. Trigger with phrases like "palantir CI", "foundry GitHub Actions", "palantir automated tests", "CI foundry". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-ci-integration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Palantir CI Integration ## Overview Set up GitHub Actions CI pipelines for Foundry integrations. Covers running transform unit tests with PySpark, SDK integration tests with mocked APIs, and linting Foundry-specific patterns. ## Prerequisites - GitHub repository with Foundry integration code - `foundry-platform-sdk` in requirements - pytest test suite ## Instructions ### Step 1: GitHub Actions Workflow ```yaml # .github/workflows/foundry-ci.yml name: Foundry CI on: push: branches: [main] pull_request: jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: python-version: "3.11" cache: pip - name: Set up Java (for PySpark) uses: actions/setup-java@v4 with: distribution: temurin java-version: "11" - name: Install dependencies run: pip install -r requirements.txt - name: Run unit tests run: pytest tests/ -v --tb=short --junitxml=test-results.xml - name: Upload test results if: always() uses: actions/upload-artifact@v4 with: name: test-results path: test-results.xml lint: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-python@v5 with: python-version: "3.11" - run: pip install ruff
- Overview
- Prerequisites
- Instructions
- Step 1: GitHub Actions Workflow
- Step 2: Secret Configuration
- Step 3: Custom Linting Rules for Foundry
- Output
- Error Handling
- Resources
- Next Steps
Add secrets to GitHub repository gh secret set FOUNDRY_HOSTNAME --body "mycompany.palantirfoundry.com" gh secret set FOUNDRY_CLIENT_ID --body "your-client-id" gh secret set FOUNDRY_CLIENT_SECRET --body "your-client-secret"
What does the palantir-ci-integration skill do?
Configure CI/CD pipelines for Palantir Foundry integrations with GitHub Actions. Use when setting up automated testing, running transforms validation, or integrating Foundry SDK tests into your build process. Trigger with phrases like "palantir CI", "foundry GitHub Actions", "palantir automated tests", "CI foundry". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-ci-integration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.