Skip to content
TrustedSkillsbeta
Back to all skills

Ssdt Cicd Best Practices 2025

Checked
josiahsiegel·vlatest·devops·MIT

Helps with CI/CD, best practices as part of automating DevOps pipelines and CI/CD workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add josiahsiegel/claude-plugin-marketplace --skill ssdt-cicd-best-practices-2025 -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

josiahsiegel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a1b1123b9
Manifest
plugins/ssdt-master/skills/ssdt-cicd-best-practices-2025/SKILL.md
Scanned
2 files, 652 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance and best practices for implementing CI/CD pipelines specifically tailored to SQL Server database projects using SSDT, SqlPackage, and modern DevOps workflows. It emphasizes a state-based deployment approach where source code represents the desired database state rather than relying on migration scripts. The skill also highlights the importance of tSQLt unit testing within these automated pipelines.

When to use it

  • When setting up or improving CI/CD pipelines for SQL Server database projects.
  • If you're transitioning from a migration-based deployment strategy to a state-based approach.
  • To integrate robust unit testing (using tSQLt) into your DevOps pipeline.
  • For automating the build and deployment of SQL Server databases using SSDT and SqlPackage.

Key capabilities

  • State-Based Deployment: Guidance on defining database objects in .sql files for automated incremental script generation.
  • SqlPackage Integration: Instructions for utilizing SqlPackage commands within CI/CD pipelines (e.g., publishing DACPACs).
  • tSQLt Unit Testing: Recommendations and integration strategies for using the tSQLt framework for SQL Server unit testing. Includes features like automatic transactions, schema grouping, mocking, and assertions.
  • Windows File Path Conventions: Strict enforcement of backslash usage () in file paths when interacting with Windows systems via Edit or Write tools.

Example prompts

  • "How can I implement state-based deployment for my SQL Server database project using SSDT?"
  • "What's the best way to integrate tSQLt unit testing into a GitHub Actions pipeline?"
  • "Show me an example of how to publish a DACPAC file using SqlPackage in a CI/CD workflow."
  • “Why should I use backslashes instead of forward slashes for file paths?”

Tips & gotchas

  • Windows File Paths: Always use backslashes (\) when specifying file paths on Windows systems. Forward slashes will cause errors.
  • Documentation: Avoid creating new documentation files unless explicitly requested; prioritize updating existing README.md files.
  • State-Based vs. Migration-Based: Understand the fundamental differences between state-based and migration-based deployment approaches to choose the right strategy for your project.