deploysharp-package-release
Skill179 starsChanged 12 days agoApache-2.0View on GitHub
Prepare, verify, pack, or publish DeploySharp NuGet packages and coordinated GitHub release assets. Use for versioning, package boundaries, release workflows, or publication; publishing requires explicit user authorization.
In this repository5 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read Directory.Build.props, the target .csproj, .github/workflows/ci.yml, .github/workflows/publish-nuget.yml, and …
- Distinctive: line 14
Ensure adapters do not accidentally embed third-party native runtimes that the final application is expected to select.
- Distinctive: line 23
Do not replace immutable model assets in place.
- Distinctive: line 27
Run git diff --check, focused tests, package creation, and package-content inspection.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DeploySharp Package And Release
Preserve the repository's package boundaries. Each project under src is an independently versioned NuGet package unless an approved architecture change says otherwise.
Preflight
- Read
Directory.Build.props, the target.csproj,.github/workflows/ci.yml,.github/workflows/publish-nuget.yml, anddocs/articles/package-combinations.md. - Confirm package ID, target frameworks, project references, public dependencies, native-runtime ownership, symbols/source metadata, and version source.
- Ensure adapters do not accidentally embed third-party native runtimes that the final application is expected to select.
- Build and test the affected projects on their declared target frameworks, then create packages in a clean output directory and inspect archive contents.
Package restore success is not runtime validation. For native backends, also verify a clean consumer and missing-native diagnostic when those fixtures exist.
Publication Boundary
Packing and local inspection are reversible. NuGet push, GitHub Release creation or modification, asset upload/removal, tags, and GitHub Packages publication are external mutations: perform them only when the user explicitly requests publication and the authenticated account/repository are confirmed.
Do not replace immutable model assets in place. Publish a new revision, update hashes and catalog entries, and keep backend/device-specific TensorRT engines out of portable Releases unless the asset is clearly scoped.
Completion
Run git diff --check, focused tests, package creation, and package-content inspection. Keep preview and stable release notes aligned with the actual version. Report anything not tested; do not describe a package as published until the registry confirms it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.