How do I install the Snickler Squad Sdk Net Git Workflow skill?

Run npx skillmds@latest add tomevault-io/snickler-squad-sdk-net-git-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Snickler Squad Sdk Net Git Workflow skill do?

Context It is listed under Productivity on SkillMD.

Is Snickler Squad Sdk Net Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Snickler Squad Sdk Net Git Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Snickler Squad Sdk Net Git Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Snickler Squad Sdk Net Git Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Snickler Squad Sdk Net Git Workflow by tomevault-io

Name: Snickler Squad Sdk Net Git Workflow
Author: tomevault-io

File contents

Context

Squad.SDK.NET uses three long-lived branches:

Branch	Purpose	Notes
`dev`	Integration branch for feature work	PRs target `dev`; releaseable SDK changes add `.changeset` files
`preview`	Release candidate branch	Promotion from `dev` applies changesets into csproj version + changelog
`main`	Stable released branch	Pushes trigger automatic tagging and NuGet/GitHub release creation

Workflow for Issue Work

Branch from dev.
Do the work and add tests.
If you changed releaseable SDK behavior under src/Squad.SDK.NET/, add a .changeset/*.md file.
Open the PR against dev.
After merge, maintainers promote dev -> preview with promote.yml.
After preview validation passes, maintainers promote preview -> main.

Changeset Rule

Releaseable SDK changes need a changeset:

---
"Squad.SDK.NET": minor
---

Add preview validation for release candidates.

Use:

patch for backwards-compatible fixes
minor for backwards-compatible features
major for breaking API changes

Promotion Pipeline

dev -> preview: merge dev, apply changesets, bump csproj version, update changelog, clear applied changesets
preview -> main: merge validated preview into main
main: creates v<Version> automatically and publishes the stable release
main -> dev: the release commit is synced back into dev so new changesets start from the released baseline

Anti-Patterns

❌ Branching from main for normal feature work
❌ PRs targeting main directly
❌ Pushing manual release tags
❌ Skipping .changeset files for releaseable SDK changes
❌ Leaving pending changesets on preview or main

Source: snickler/squad-sdk-net — distributed by TomeVault.

---name: snickler-squad-sdk-net-git-workflowdescription: Context---## ContextSquad.SDK.NET uses three long-lived branches:| Branch | Purpose | Notes ||--------|---------|-------|| `dev` | Integration branch for feature work | PRs target `dev`; releaseable SDK changes add `.changeset` files || `preview` | Release candidate branch | Promotion from `dev` applies changesets into csproj version + changelog || `main` | Stable released branch | Pushes trigger automatic tagging and NuGet/GitHub release creation |## Workflow for Issue Work1. Branch from `dev`.2. Do the work and add tests.3. If you changed releaseable SDK behavior under `src/Squad.SDK.NET/`, add a `.changeset/*.md` file.4. Open the PR against `dev`.5. After merge, maintainers promote `dev -> preview` with `promote.yml`.6. After preview validation passes, maintainers promote `preview -> main`.## Changeset RuleReleaseable SDK changes need a changeset:```md---"Squad.SDK.NET": minor---Add preview validation for release candidates.```Use:- `patch` for backwards-compatible fixes- `minor` for backwards-compatible features- `major` for breaking API changes## Promotion Pipeline- `dev -> preview`: merge dev, apply changesets, bump csproj version, update changelog, clear applied changesets- `preview -> main`: merge validated preview into main- `main`: creates `v<Version>` automatically and publishes the stable release- `main -> dev`: the release commit is synced back into dev so new changesets start from the released baseline## Anti-Patterns- ❌ Branching from `main` for normal feature work- ❌ PRs targeting `main` directly- ❌ Pushing manual release tags- ❌ Skipping `.changeset` files for releaseable SDK changes- ❌ Leaving pending changesets on `preview` or `main`---> Source: [snickler/squad-sdk-net](https://github.com/snickler/squad-sdk-net) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Snickler Squad Sdk Net Git Workflow