Agent skill · software engineering · jeremylongshore
documenso-ci-integration
Configure CI/CD pipelines for Documenso integrations.
Why this skill is useful
Provides specific CI/CD pipeline configurations and testing workflows for Documenso that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. Requires documenso, github account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Documenso CI Integration Output A credential-free pull-request lane for schema/template/unit checks and a trusted, scoped development integration lane. A redacted CI receipt with validation outcome and a safe failure/retry procedure. Examples Run template/schema/unit checks on every pull request using synthetic documents and signers, then execute one protected-branch development integration check with a scoped secret. If it fails, retain redacted correlation/status evidence; never expose signing credentials, document payloads, or production workspace access to forked CI code. Overview Configure CI/CD pipelines for Documenso integrations with GitHub Actions. Covers unit testing with mocks, integration testing against staging, and deployment workflows with secret management. Prerequisites GitHub repository with Actions enabled Documenso staging API key Test environment configured (see documenso-local-dev-loop) Instructions Step 1: GitHub Actions Workflow Step 2: Unit Tests with Mocked SDK Step 3: Integration Tests Against Staging Step 4: Add Secrets to GitHub Step 5: Package.json Scripts Step 6: Pre-commit Hook (Optional) This runs unit tests (with mocks) before every commit, catching issues early without needing API access. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/documenso-ci-integration--1a59f3