agentleFS
EvotecITEvotecIT/OfficeIMO/.agents/skills/officeimo-build-release/SKILL.md

officeimo-build-release

Skill713 starsChanged yesterdayMITView on GitHub

Use when building, packaging, releasing, or validating OfficeIMO and PSWriteOffice artifacts. Prefer repo-standard build and PowerForge/PSPublishModule entrypoints over consumer-local packaging logic.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for OfficeIMO build, package, release, website, and downstream validation work.

    line 8
  2. Very specific:

    Use Build/Build-Release.ps1 for coordinated OfficeIMO/PSWriteOffice builds and publication.

    line 14
  3. Very specific:

    Use Build/Build-Module.ps1 -IncludePackages:$false only for local unsigned module iteration.

    line 15
  4. Distinctive:

    Use solution and project builds for local compile evidence.

    line 16
  5. Very specific:

    Use Website/build.ps1 and website pipeline files for OfficeIMO.com changes.

    line 17
  6. Distinctive:

    Use shared PowerForge or PSPublishModule behavior when packaging logic is involved.

    line 18
  7. Distinctive:

    Keep generated output narrow.

    line 19
  8. Distinctive:

    If docs are generated, update the source of truth and regenerate.

    line 20
  9. Distinctive:

    If a validation command dirties broad generated docs outside the intended change, inspect and keep only intentional files.

    line 21
  10. Distinctive:

    Run the smallest useful subset when the task is narrow, and expand when public contracts, packaging, or generated website output changes.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OfficeIMO Build Release

Use this skill for OfficeIMO build, package, release, website, and downstream validation work.

Golden Path

  1. Inspect the current branch and dirty state first.
  2. Prefer repo-standard entrypoints.
    • Use Build/Build-Release.ps1 for coordinated OfficeIMO/PSWriteOffice builds and publication; see Docs/building-and-releasing.md.
    • Use Build/Build-Module.ps1 -IncludePackages:$false only for local unsigned module iteration.
    • Use solution and project builds for local compile evidence.
    • Use Website/build.ps1 and website pipeline files for OfficeIMO.com changes.
    • Use shared PowerForge or PSPublishModule behavior when packaging logic is involved.
  3. Keep generated output narrow.
    • If docs are generated, update the source of truth and regenerate.
    • If a validation command dirties broad generated docs outside the intended change, inspect and keep only intentional files.
  4. Distinguish release layers before answering whether a fix is available.
    • Local source
    • Open PR
    • Merged branch
    • Release tag
    • NuGet or PSGallery package
    • Installed downstream version
  5. For PDF or conversion release work, include at least one artifact-level proof, not just compile success.

Useful Checks

dotnet build OfficeIMO.slnx -c Release
dotnet test OfficeIMO.Word.Tests\OfficeIMO.Word.Tests.csproj -c Release
dotnet test OfficeIMO.Excel.Tests\OfficeIMO.Excel.Tests.csproj -c Release
dotnet test OfficeIMO.Shared.Tests\OfficeIMO.Shared.Tests.csproj -c Release
pwsh Website\build.ps1 -Mode dev
git diff --check

Run the smallest useful subset when the task is narrow, and expand when public contracts, packaging, or generated website output changes.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.