Skip to content

GitHub Release Skill#1561

Closed
amorguettinogueira wants to merge 5 commits intogithub:stagedfrom
amorguettinogueira:github-release-skill
Closed

GitHub Release Skill#1561
amorguettinogueira wants to merge 5 commits intogithub:stagedfrom
amorguettinogueira:github-release-skill

Conversation

@amorguettinogueira
Copy link
Copy Markdown
Contributor

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the staged branch for this pull request.

Description

This skill automates the full release workflow for a single-package GitHub repository, from analysis through changelog authoring and PR creation. It relies exclusively on gh (GitHub CLI) and git - no other tools needed.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes

N/A


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

github-actions Bot and others added 4 commits April 28, 2026 07:34
Introduce a new github-release skill that automates end-to-end library releases (SemVer decisions, changelog authoring, release branch/PR creation) relying on gh and git. Adds skill definition (skills/github-release/SKILL.md), two reference guides for commit classification and SemVer rules (references/commit-classification.md, references/semver-rules.md), and updates docs/README.skills.md to list the new skill.
Add PowerShell variants for the release workflow and note Windows users should prefer PowerShell. New snippets include: git fetch --tags; semantic latest-tag lookup and fallback to repo root commit; computing prevSha; focused git diff excluding tests/docs/lock files; a release PR body template and gh pr create invocation. Also add a Troubleshooting in PowerShell section with tips to ensure gh.exe is invoked and verify basic commands (gh --version, git fetch --tags, run the prevTag snippet). These additions provide parity with the existing Bash examples and help Windows contributors perform releases reliably.
Add guidance to always use --body-file when creating PRs to avoid literal "\n" sequences in PowerShell. Document that PowerShell here-strings preserve actual newlines, update the example to build the PR body with a here-string, write it to release_pr_body.md using Out-File -NoNewline, and adjust code fences and PR instructions accordingly.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 29, 2026

🔍 Skill Validator Results

⛔ Findings need attention

Scope Checked
Skills 135
Agents 1
Total 136
Severity Count
--- ---:
❌ Errors 19
⚠️ Warnings 128
ℹ️ Advisories 0

Summary

Level Finding
[geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference 'assets/example/01-user-input-rfc8805-feed.csv' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference './run/data/comments.json' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference './run/data/mcp-server-payload.json' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference './run/data/mcp-server-payload.json' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md.
[geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md.
Duplicate skill name 'azure-resource-health-diagnose' found in 'plugins/devops-oncall/skills/azure-resource-health-diagnose' (first seen in 'plugins/azure-cloud-development/skills/azure-resource-health-diagnose')
Duplicate skill name 'openapi-to-application-code' found in 'plugins/openapi-to-application-go/skills/openapi-to-application-code' (first seen in 'plugins/openapi-to-application-csharp-dotnet/skills/openapi-to-application-code')
Full validator output ```text Found 135 skill(s) [github-release] 📊 github-release: 3,640 BPE tokens [chars/4: 3,577] (standard ~), 43 sections, 19 code blocks [github-release] ⚠ Skill is 3,640 BPE tokens (chars/4 estimate: 3,577) — approaching "comprehensive" range where gains diminish. [ai-team-orchestration] 📊 ai-team-orchestration: 1,436 BPE tokens [chars/4: 1,400] (detailed ✓), 13 sections, 5 code blocks [arize-ai-provider-integration] 📊 arize-ai-provider-integration: 2,305 BPE tokens [chars/4: 2,216] (detailed ✓), 29 sections, 16 code blocks [arize-ai-provider-integration] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [arize-annotation] 📊 arize-annotation: 1,822 BPE tokens [chars/4: 1,930] (detailed ✓), 18 sections, 7 code blocks [arize-annotation] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [arize-dataset] 📊 arize-dataset: 3,482 BPE tokens [chars/4: 3,444] (standard ~), 51 sections, 16 code blocks [arize-dataset] ⚠ Skill is 3,482 BPE tokens (chars/4 estimate: 3,444) — approaching "comprehensive" range where gains diminish. [arize-evaluator] 📊 arize-evaluator: 6,243 BPE tokens [chars/4: 6,326] (comprehensive ✗), 57 sections, 22 code blocks [arize-evaluator] ⚠ Skill is 6,243 BPE tokens (chars/4 estimate: 6,326) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [arize-experiment] 📊 arize-experiment: 3,204 BPE tokens [chars/4: 3,167] (standard ~), 33 sections, 18 code blocks [arize-experiment] ⚠ Skill is 3,204 BPE tokens (chars/4 estimate: 3,167) — approaching "comprehensive" range where gains diminish. [arize-instrumentation] 📊 arize-instrumentation: 4,790 BPE tokens [chars/4: 4,901] (standard ~), 19 sections, 3 code blocks [arize-instrumentation] ⚠ Skill is 4,790 BPE tokens (chars/4 estimate: 4,901) — approaching "comprehensive" range where gains diminish. [arize-link] 📊 arize-link: 1,191 BPE tokens [chars/4: 1,073] (detailed ✓), 9 sections, 6 code blocks [arize-prompt-optimization] 📊 arize-prompt-optimization: 4,296 BPE tokens [chars/4: 4,594] (standard ~), 58 sections, 19 code blocks [arize-prompt-optimization] ⚠ Skill is 4,296 BPE tokens (chars/4 estimate: 4,594) — approaching "comprehensive" range where gains diminish. [arize-trace] 📊 arize-trace: 5,220 BPE tokens [chars/4: 5,151] (comprehensive ✗), 42 sections, 10 code blocks [arize-trace] ⚠ Skill is 5,220 BPE tokens (chars/4 estimate: 5,151) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [automate-this] 📊 automate-this: 2,869 BPE tokens [chars/4: 3,107] (standard ~), 16 sections, 8 code blocks [automate-this] ⚠ Skill is 2,869 BPE tokens (chars/4 estimate: 3,107) — approaching "comprehensive" range where gains diminish. [suggest-awesome-github-copilot-agents] 📊 suggest-awesome-github-copilot-agents: 1,467 BPE tokens [chars/4: 1,979] (detailed ✓), 9 sections, 0 code blocks [suggest-awesome-github-copilot-agents] ⚠ No code blocks — agents perform better with concrete snippets and commands. [suggest-awesome-github-copilot-instructions] 📊 suggest-awesome-github-copilot-instructions: 1,499 BPE tokens [chars/4: 1,904] (detailed ✓), 11 sections, 1 code blocks [suggest-awesome-github-copilot-skills] 📊 suggest-awesome-github-copilot-skills: 1,725 BPE tokens [chars/4: 2,018] (detailed ✓), 11 sections, 1 code blocks [az-cost-optimize] 📊 az-cost-optimize: 2,956 BPE tokens [chars/4: 3,218] (standard ~), 12 sections, 7 code blocks [az-cost-optimize] ⚠ Skill is 2,956 BPE tokens (chars/4 estimate: 3,218) — approaching "comprehensive" range where gains diminish. [azure-pricing] 📊 azure-pricing: 2,315 BPE tokens [chars/4: 2,371] (detailed ✓), 23 sections, 4 code blocks [azure-resource-health-diagnose] 📊 azure-resource-health-diagnose: 2,492 BPE tokens [chars/4: 2,859] (detailed ✓), 12 sections, 8 code blocks [import-infrastructure-as-code] 📊 import-infrastructure-as-code: 4,135 BPE tokens [chars/4: 4,680] (standard ~), 30 sections, 11 code blocks [import-infrastructure-as-code] ⚠ Skill is 4,135 BPE tokens (chars/4 estimate: 4,680) — approaching "comprehensive" range where gains diminish. [remember-interactive-programming] 📊 remember-interactive-programming: 175 BPE tokens [chars/4: 221] (compact ✓), 0 sections, 0 code blocks [remember-interactive-programming] ⚠ Skill is only 175 BPE tokens (chars/4 estimate: 221) — may be too sparse to provide actionable guidance. [remember-interactive-programming] ⚠ No section headers — agents navigate structured documents better. [remember-interactive-programming] ⚠ No code blocks — agents perform better with concrete snippets and commands. [remember-interactive-programming] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [context-map] 📊 context-map: 249 BPE tokens [chars/4: 287] (compact ✓), 10 sections, 1 code blocks [refactor-plan] 📊 refactor-plan: 356 BPE tokens [chars/4: 355] (compact ✓), 15 sections, 1 code blocks [what-context-needed] 📊 what-context-needed: 209 BPE tokens [chars/4: 219] (compact ✓), 9 sections, 1 code blocks [integrate-context-matic] 📊 integrate-context-matic: 1,496 BPE tokens [chars/4: 1,574] (detailed ✓), 12 sections, 0 code blocks [integrate-context-matic] ⚠ No code blocks — agents perform better with concrete snippets and commands. [integrate-context-matic] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [onboard-context-matic] 📊 onboard-context-matic: 3,136 BPE tokens [chars/4: 3,361] (standard ~), 13 sections, 12 code blocks [onboard-context-matic] ⚠ Skill is 3,136 BPE tokens (chars/4 estimate: 3,361) — approaching "comprehensive" range where gains diminish. [copilot-sdk] 📊 copilot-sdk: 5,749 BPE tokens [chars/4: 6,042] (comprehensive ✗), 63 sections, 41 code blocks [copilot-sdk] ⚠ Skill is 5,749 BPE tokens (chars/4 estimate: 6,042) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [aspnet-minimal-api-openapi] 📊 aspnet-minimal-api-openapi: 343 BPE tokens [chars/4: 439] (compact ✓), 5 sections, 0 code blocks [aspnet-minimal-api-openapi] ⚠ No code blocks — agents perform better with concrete snippets and commands. [aspnet-minimal-api-openapi] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [csharp-async] 📊 csharp-async: 379 BPE tokens [chars/4: 466] (compact ✓), 7 sections, 0 code blocks [csharp-async] ⚠ No code blocks — agents perform better with concrete snippets and commands. [csharp-async] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [csharp-mstest] 📊 csharp-mstest: 3,249 BPE tokens [chars/4: 3,458] (standard ~), 31 sections, 22 code blocks [csharp-mstest] ⚠ Skill is 3,249 BPE tokens (chars/4 estimate: 3,458) — approaching "comprehensive" range where gains diminish. [csharp-nunit] 📊 csharp-nunit: 636 BPE tokens [chars/4: 711] (detailed ✓), 8 sections, 0 code blocks [csharp-nunit] ⚠ No code blocks — agents perform better with concrete snippets and commands. [csharp-nunit] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [csharp-tunit] 📊 csharp-tunit: 1,164 BPE tokens [chars/4: 1,287] (detailed ✓), 10 sections, 0 code blocks [csharp-tunit] ⚠ No code blocks — agents perform better with concrete snippets and commands. [csharp-tunit] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [csharp-xunit] 📊 csharp-xunit: 599 BPE tokens [chars/4: 677] (detailed ✓), 8 sections, 0 code blocks [csharp-xunit] ⚠ No code blocks — agents perform better with concrete snippets and commands. [csharp-xunit] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [dotnet-best-practices] 📊 dotnet-best-practices: 602 BPE tokens [chars/4: 808] (detailed ✓), 12 sections, 0 code blocks [dotnet-best-practices] ⚠ No code blocks — agents perform better with concrete snippets and commands. [dotnet-best-practices] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [dotnet-upgrade] 📊 dotnet-upgrade: 1,354 BPE tokens [chars/4: 1,768] (detailed ✓), 1 sections, 0 code blocks [dotnet-upgrade] ⚠ No code blocks — agents perform better with concrete snippets and commands. [dotnet-upgrade] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [csharp-mcp-server-generator] 📊 csharp-mcp-server-generator: 459 BPE tokens [chars/4: 560] (detailed ✓), 9 sections, 0 code blocks [csharp-mcp-server-generator] ⚠ No code blocks — agents perform better with concrete snippets and commands. [postgresql-code-review] 📊 postgresql-code-review: 1,646 BPE tokens [chars/4: 1,847] (detailed ✓), 21 sections, 8 code blocks [postgresql-optimization] 📊 postgresql-optimization: 2,651 BPE tokens [chars/4: 2,834] (standard ~), 36 sections, 20 code blocks [postgresql-optimization] ⚠ Skill is 2,651 BPE tokens (chars/4 estimate: 2,834) — approaching "comprehensive" range where gains diminish. [postgresql-optimization] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [sql-code-review] 📊 sql-code-review: 2,112 BPE tokens [chars/4: 2,220] (detailed ✓), 36 sections, 15 code blocks [sql-optimization] 📊 sql-optimization: 2,212 BPE tokens [chars/4: 2,298] (detailed ✓), 28 sections, 14 code blocks [dataverse-python-advanced-patterns] 📊 dataverse-python-advanced-patterns: 242 BPE tokens [chars/4: 291] (compact ✓), 0 sections, 0 code blocks [dataverse-python-advanced-patterns] ⚠ No section headers — agents navigate structured documents better. [dataverse-python-advanced-patterns] ⚠ No code blocks — agents perform better with concrete snippets and commands. [dataverse-python-production-code] 📊 dataverse-python-production-code: 813 BPE tokens [chars/4: 913] (detailed ✓), 9 sections, 3 code blocks [dataverse-python-quickstart] 📊 dataverse-python-quickstart: 133 BPE tokens [chars/4: 163] (compact ✓), 0 sections, 0 code blocks [dataverse-python-quickstart] ⚠ Skill is only 133 BPE tokens (chars/4 estimate: 163) — may be too sparse to provide actionable guidance. [dataverse-python-quickstart] ⚠ No section headers — agents navigate structured documents better. [dataverse-python-quickstart] ⚠ No code blocks — agents perform better with concrete snippets and commands. [dataverse-python-quickstart] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [dataverse-python-usecase-builder] 📊 dataverse-python-usecase-builder: 1,538 BPE tokens [chars/4: 1,684] (detailed ✓), 38 sections, 5 code blocks [azure-resource-health-diagnose] 📊 azure-resource-health-diagnose: 2,492 BPE tokens [chars/4: 2,859] (detailed ✓), 12 sections, 8 code blocks [multi-stage-dockerfile] 📊 multi-stage-dockerfile: 443 BPE tokens [chars/4: 577] (detailed ✓), 5 sections, 0 code blocks [multi-stage-dockerfile] ⚠ No code blocks — agents perform better with concrete snippets and commands. [multi-stage-dockerfile] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [doublecheck] 📊 doublecheck: 3,254 BPE tokens [chars/4: 3,973] (standard ~), 26 sections, 3 code blocks [doublecheck] ⚠ Skill is 3,254 BPE tokens (chars/4 estimate: 3,973) — approaching "comprehensive" range where gains diminish. [from-the-other-side-vega] 📊 from-the-other-side-vega: 820 BPE tokens [chars/4: 894] (detailed ✓), 9 sections, 0 code blocks [from-the-other-side-vega] ⚠ No code blocks — agents perform better with concrete snippets and commands. [from-the-other-side-vega] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [geofeed-tuner] 📊 geofeed-tuner: 11,662 BPE tokens [chars/4: 12,215] (comprehensive ✗), 35 sections, 15 code blocks ❌ [geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference 'assets/example/01-user-input-rfc8805-feed.csv' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference './run/data/comments.json' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference './run/data/mcp-server-payload.json' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference './run/data/mcp-server-payload.json' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md. ❌ [geofeed-tuner] File reference './run/data/report-data.json' is 2 directories deep — maximum is 1 level from SKILL.md. [geofeed-tuner] ⚠ Skill is 11,662 BPE tokens (chars/4 estimate: 12,215) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [flowstudio-power-automate-build] 📊 flowstudio-power-automate-build: 4,461 BPE tokens [chars/4: 4,595] (standard ~), 40 sections, 15 code blocks [flowstudio-power-automate-build] ⚠ Skill is 4,461 BPE tokens (chars/4 estimate: 4,595) — approaching "comprehensive" range where gains diminish. [flowstudio-power-automate-build] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [flowstudio-power-automate-debug] 📊 flowstudio-power-automate-debug: 4,119 BPE tokens [chars/4: 4,060] (standard ~), 64 sections, 15 code blocks [flowstudio-power-automate-debug] ⚠ Skill is 4,119 BPE tokens (chars/4 estimate: 4,060) — approaching "comprehensive" range where gains diminish. [flowstudio-power-automate-governance] 📊 flowstudio-power-automate-governance: 5,229 BPE tokens [chars/4: 5,609] (comprehensive ✗), 17 sections, 11 code blocks [flowstudio-power-automate-governance] ⚠ Skill is 5,229 BPE tokens (chars/4 estimate: 5,609) — "comprehensive" skills hurt performance by 2.9pp on average. Consider splitting into 2–3 focused skills. [flowstudio-power-automate-mcp] 📊 flowstudio-power-automate-mcp: 4,716 BPE tokens [chars/4: 4,522] (standard ~), 62 sections, 11 code blocks [flowstudio-power-automate-mcp] ⚠ Skill is 4,716 BPE tokens (chars/4 estimate: 4,522) — approaching "comprehensive" range where gains diminish. [flowstudio-power-automate-mcp] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [flowstudio-power-automate-monitoring] 📊 flowstudio-power-automate-monitoring: 3,546 BPE tokens [chars/4: 3,354] (standard ~), 25 sections, 14 code blocks [flowstudio-power-automate-monitoring] ⚠ Skill is 3,546 BPE tokens (chars/4 estimate: 3,354) — approaching "comprehensive" range where gains diminish. [playwright-explore-website] 📊 playwright-explore-website: 140 BPE tokens [chars/4: 171] (compact ✓), 2 sections, 0 code blocks [playwright-explore-website] ⚠ Skill is only 140 BPE tokens (chars/4 estimate: 171) — may be too sparse to provide actionable guidance. [playwright-explore-website] ⚠ No code blocks — agents perform better with concrete snippets and commands. [playwright-generate-test] 📊 playwright-generate-test: 178 BPE tokens [chars/4: 220] (compact ✓), 2 sections, 0 code blocks [playwright-generate-test] ⚠ Skill is only 178 BPE tokens (chars/4 estimate: 220) — may be too sparse to provide actionable guidance. [playwright-generate-test] ⚠ No code blocks — agents perform better with concrete snippets and commands. [playwright-generate-test] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [go-mcp-server-generator] 📊 go-mcp-server-generator: 1,740 BPE tokens [chars/4: 1,759] (detailed ✓), 21 sections, 8 code blocks [create-spring-boot-java-project] 📊 create-spring-boot-java-project: 1,092 BPE tokens [chars/4: 1,138] (detailed ✓), 17 sections, 11 code blocks [create-spring-boot-java-project] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [java-docs] 📊 java-docs: 316 BPE tokens [chars/4: 360] (compact ✓), 1 sections, 0 code blocks [java-docs] ⚠ No code blocks — agents perform better with concrete snippets and commands. [java-docs] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [java-junit] 📊 java-junit: 695 BPE tokens [chars/4: 746] (detailed ✓), 8 sections, 0 code blocks [java-junit] ⚠ No code blocks — agents perform better with concrete snippets and commands. [java-junit] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [java-springboot] 📊 java-springboot: 855 BPE tokens [chars/4: 1,034] (detailed ✓), 10 sections, 0 code blocks [java-springboot] ⚠ No code blocks — agents perform better with concrete snippets and commands. [java-springboot] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [java-mcp-server-generator] 📊 java-mcp-server-generator: 4,637 BPE tokens [chars/4: 5,506] (standard ~), 28 sections, 19 code blocks [java-mcp-server-generator] ⚠ Skill is 4,637 BPE tokens (chars/4 estimate: 5,506) — approaching "comprehensive" range where gains diminish. [kotlin-mcp-server-generator] 📊 kotlin-mcp-server-generator: 2,456 BPE tokens [chars/4: 2,672] (detailed ✓), 29 sections, 13 code blocks [mcp-create-adaptive-cards] 📊 mcp-create-adaptive-cards: 2,949 BPE tokens [chars/4: 3,136] (standard ~), 33 sections, 22 code blocks [mcp-create-adaptive-cards] ⚠ Skill is 2,949 BPE tokens (chars/4 estimate: 3,136) — approaching "comprehensive" range where gains diminish. [mcp-create-declarative-agent] 📊 mcp-create-declarative-agent: 1,978 BPE tokens [chars/4: 2,036] (detailed ✓), 30 sections, 12 code blocks [mcp-deploy-manage-agents] 📊 mcp-deploy-manage-agents: 2,036 BPE tokens [chars/4: 2,471] (detailed ✓), 49 sections, 2 code blocks [napkin] 📊 napkin: 1,649 BPE tokens [chars/4: 1,784] (detailed ✓), 12 sections, 4 code blocks [noob-mode] 📊 noob-mode: 2,604 BPE tokens [chars/4: 2,765] (standard ~), 13 sections, 9 code blocks [noob-mode] ⚠ Skill is 2,604 BPE tokens (chars/4 estimate: 2,765) — approaching "comprehensive" range where gains diminish. [openapi-to-application-code] 📊 openapi-to-application-code: 931 BPE tokens [chars/4: 1,144] (detailed ✓), 11 sections, 1 code blocks [openapi-to-application-code] 📊 openapi-to-application-code: 931 BPE tokens [chars/4: 1,144] (detailed ✓), 11 sections, 1 code blocks [openapi-to-application-code] 📊 openapi-to-application-code: 931 BPE tokens [chars/4: 1,144] (detailed ✓), 11 sections, 1 code blocks [openapi-to-application-code] 📊 openapi-to-application-code: 931 BPE tokens [chars/4: 1,144] (detailed ✓), 11 sections, 1 code blocks [openapi-to-application-code] 📊 openapi-to-application-code: 931 BPE tokens [chars/4: 1,144] (detailed ✓), 11 sections, 1 code blocks [creating-oracle-to-postgres-master-migration-plan] 📊 creating-oracle-to-postgres-master-migration-plan: 755 BPE tokens [chars/4: 790] (detailed ✓), 6 sections, 2 code blocks [creating-oracle-to-postgres-migration-bug-report] 📊 creating-oracle-to-postgres-migration-bug-report: 473 BPE tokens [chars/4: 567] (detailed ✓), 6 sections, 0 code blocks [creating-oracle-to-postgres-migration-bug-report] ⚠ No code blocks — agents perform better with concrete snippets and commands. [creating-oracle-to-postgres-migration-bug-report] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [creating-oracle-to-postgres-migration-integration-tests] 📊 creating-oracle-to-postgres-migration-integration-tests: 605 BPE tokens [chars/4: 760] (detailed ✓), 4 sections, 1 code blocks [creating-oracle-to-postgres-migration-integration-tests] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [migrating-oracle-to-postgres-stored-procedures] 📊 migrating-oracle-to-postgres-stored-procedures: 493 BPE tokens [chars/4: 576] (detailed ✓), 2 sections, 1 code blocks [migrating-oracle-to-postgres-stored-procedures] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [planning-oracle-to-postgres-migration-integration-testing] 📊 planning-oracle-to-postgres-migration-integration-testing: 438 BPE tokens [chars/4: 547] (detailed ✓), 4 sections, 1 code blocks [planning-oracle-to-postgres-migration-integration-testing] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [reviewing-oracle-to-postgres-migration] 📊 reviewing-oracle-to-postgres-migration: 605 BPE tokens [chars/4: 762] (detailed ✓), 5 sections, 2 code blocks [scaffolding-oracle-to-postgres-migration-test-project] 📊 scaffolding-oracle-to-postgres-migration-test-project: 527 BPE tokens [chars/4: 632] (detailed ✓), 3 sections, 1 code blocks [scaffolding-oracle-to-postgres-migration-test-project] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [sponsor-finder] 📊 sponsor-finder: 3,085 BPE tokens [chars/4: 2,991] (standard ~), 25 sections, 6 code blocks [sponsor-finder] ⚠ Skill is 3,085 BPE tokens (chars/4 estimate: 2,991) — approaching "comprehensive" range where gains diminish. [phoenix-cli] 📊 phoenix-cli: 1,615 BPE tokens [chars/4: 1,563] (detailed ✓), 13 sections, 12 code blocks [phoenix-cli] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [phoenix-evals] 📊 phoenix-evals: 1,089 BPE tokens [chars/4: 1,126] (detailed ✓), 5 sections, 0 code blocks [phoenix-evals] ⚠ No code blocks — agents perform better with concrete snippets and commands. [phoenix-evals] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [phoenix-tracing] 📊 phoenix-tracing: 1,488 BPE tokens [chars/4: 1,690] (detailed ✓), 17 sections, 1 code blocks [php-mcp-server-generator] 📊 php-mcp-server-generator: 2,723 BPE tokens [chars/4: 2,697] (standard ~), 37 sections, 25 code blocks [php-mcp-server-generator] ⚠ Skill is 2,723 BPE tokens (chars/4 estimate: 2,697) — approaching "comprehensive" range where gains diminish. [polyglot-test-agent] 📊 polyglot-test-agent: 1,611 BPE tokens [chars/4: 1,676] (detailed ✓), 22 sections, 5 code blocks [power-apps-code-app-scaffold] 📊 power-apps-code-app-scaffold: 1,424 BPE tokens [chars/4: 1,786] (detailed ✓), 18 sections, 2 code blocks [power-bi-dax-optimization] 📊 power-bi-dax-optimization: 1,114 BPE tokens [chars/4: 1,390] (detailed ✓), 18 sections, 6 code blocks [power-bi-model-design-review] 📊 power-bi-model-design-review: 2,126 BPE tokens [chars/4: 2,782] (detailed ✓), 28 sections, 17 code blocks [power-bi-performance-troubleshooting] 📊 power-bi-performance-troubleshooting: 2,078 BPE tokens [chars/4: 2,591] (detailed ✓), 31 sections, 19 code blocks [power-bi-report-design-consultation] 📊 power-bi-report-design-consultation: 2,357 BPE tokens [chars/4: 2,723] (detailed ✓), 22 sections, 13 code blocks [power-platform-architect] 📊 power-platform-architect: 3,104 BPE tokens [chars/4: 3,609] (standard ~), 12 sections, 1 code blocks [power-platform-architect] ⚠ Skill is 3,104 BPE tokens (chars/4 estimate: 3,609) — approaching "comprehensive" range where gains diminish. [mcp-copilot-studio-server-generator] 📊 mcp-copilot-studio-server-generator: 942 BPE tokens [chars/4: 1,063] (detailed ✓), 6 sections, 2 code blocks [power-platform-mcp-connector-suite] 📊 power-platform-mcp-connector-suite: 1,348 BPE tokens [chars/4: 1,590] (detailed ✓), 19 sections, 1 code blocks [power-platform-mcp-connector-suite] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [breakdown-epic-arch] 📊 breakdown-epic-arch: 601 BPE tokens [chars/4: 712] (detailed ✓), 12 sections, 0 code blocks [breakdown-epic-arch] ⚠ No code blocks — agents perform better with concrete snippets and commands. [breakdown-epic-arch] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [breakdown-epic-pm] 📊 breakdown-epic-pm: 509 BPE tokens [chars/4: 575] (detailed ✓), 13 sections, 0 code blocks [breakdown-epic-pm] ⚠ No code blocks — agents perform better with concrete snippets and commands. [breakdown-epic-pm] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [breakdown-feature-implementation] 📊 breakdown-feature-implementation: 966 BPE tokens [chars/4: 1,189] (detailed ✓), 9 sections, 2 code blocks [breakdown-feature-implementation] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [breakdown-feature-prd] 📊 breakdown-feature-prd: 557 BPE tokens [chars/4: 620] (detailed ✓), 13 sections, 0 code blocks [breakdown-feature-prd] ⚠ No code blocks — agents perform better with concrete snippets and commands. [breakdown-feature-prd] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [create-github-issues-feature-from-implementation-plan] 📊 create-github-issues-feature-from-implementation-plan: 191 BPE tokens [chars/4: 237] (compact ✓), 4 sections, 0 code blocks [create-github-issues-feature-from-implementation-plan] ⚠ Skill is only 191 BPE tokens (chars/4 estimate: 237) — may be too sparse to provide actionable guidance. [create-github-issues-feature-from-implementation-plan] ⚠ No code blocks — agents perform better with concrete snippets and commands. [create-implementation-plan] 📊 create-implementation-plan: 1,390 BPE tokens [chars/4: 1,575] (detailed ✓), 22 sections, 1 code blocks [create-implementation-plan] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [create-technical-spike] 📊 create-technical-spike: 1,358 BPE tokens [chars/4: 1,643] (detailed ✓), 33 sections, 1 code blocks [update-implementation-plan] 📊 update-implementation-plan: 1,400 BPE tokens [chars/4: 1,595] (detailed ✓), 22 sections, 1 code blocks [update-implementation-plan] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [python-mcp-server-generator] 📊 python-mcp-server-generator: 871 BPE tokens [chars/4: 990] (detailed ✓), 13 sections, 0 code blocks [python-mcp-server-generator] ⚠ No code blocks — agents perform better with concrete snippets and commands. [react-audit-grep-patterns] 📊 react-audit-grep-patterns: 475 BPE tokens [chars/4: 461] (detailed ✓), 13 sections, 1 code blocks [react-audit-grep-patterns] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [react18-batching-patterns] 📊 react18-batching-patterns: 561 BPE tokens [chars/4: 621] (detailed ✓), 4 sections, 1 code blocks [react18-batching-patterns] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [react18-dep-compatibility] 📊 react18-dep-compatibility: 1,388 BPE tokens [chars/4: 1,124] (detailed ✓), 10 sections, 1 code blocks [react18-dep-compatibility] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [react18-enzyme-to-rtl] 📊 react18-enzyme-to-rtl: 870 BPE tokens [chars/4: 917] (detailed ✓), 6 sections, 3 code blocks [react18-legacy-context] 📊 react18-legacy-context: 561 BPE tokens [chars/4: 620] (detailed ✓), 8 sections, 2 code blocks [react18-lifecycle-patterns] 📊 react18-lifecycle-patterns: 768 BPE tokens [chars/4: 910] (detailed ✓), 7 sections, 1 code blocks [react18-lifecycle-patterns] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [react18-string-refs] 📊 react18-string-refs: 549 BPE tokens [chars/4: 527] (detailed ✓), 6 sections, 1 code blocks [react19-concurrent-patterns] 📊 react19-concurrent-patterns: 681 BPE tokens [chars/4: 722] (detailed ✓), 9 sections, 5 code blocks [react19-source-patterns] 📊 react19-source-patterns: 462 BPE tokens [chars/4: 489] (detailed ✓), 4 sections, 1 code blocks [react19-source-patterns] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [react19-test-patterns] 📊 react19-test-patterns: 815 BPE tokens [chars/4: 790] (detailed ✓), 7 sections, 5 code blocks [roundup] 📊 roundup: 2,219 BPE tokens [chars/4: 2,591] (detailed ✓), 28 sections, 0 code blocks [roundup] ⚠ No code blocks — agents perform better with concrete snippets and commands. [roundup] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [roundup-setup] 📊 roundup-setup: 3,202 BPE tokens [chars/4: 3,669] (standard ~), 18 sections, 1 code blocks [roundup-setup] ⚠ Skill is 3,202 BPE tokens (chars/4 estimate: 3,669) — approaching "comprehensive" range where gains diminish. [ruby-mcp-server-generator] 📊 ruby-mcp-server-generator: 3,459 BPE tokens [chars/4: 3,631] (standard ~), 37 sections, 24 code blocks [ruby-mcp-server-generator] ⚠ Skill is 3,459 BPE tokens (chars/4 estimate: 3,631) — approaching "comprehensive" range where gains diminish. [rust-mcp-server-generator] 📊 rust-mcp-server-generator: 3,088 BPE tokens [chars/4: 3,190] (standard ~), 31 sections, 24 code blocks [rust-mcp-server-generator] ⚠ Skill is 3,088 BPE tokens (chars/4 estimate: 3,190) — approaching "comprehensive" range where gains diminish. [salesforce-apex-quality] 📊 salesforce-apex-quality: 1,682 BPE tokens [chars/4: 1,820] (detailed ✓), 14 sections, 4 code blocks [salesforce-apex-quality] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [salesforce-component-standards] 📊 salesforce-component-standards: 2,300 BPE tokens [chars/4: 2,448] (detailed ✓), 20 sections, 4 code blocks [salesforce-component-standards] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [salesforce-flow-design] 📊 salesforce-flow-design: 1,491 BPE tokens [chars/4: 1,740] (detailed ✓), 15 sections, 5 code blocks [salesforce-flow-design] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [ai-prompt-engineering-safety-review] 📊 ai-prompt-engineering-safety-review: 2,185 BPE tokens [chars/4: 2,540] (detailed ✓), 19 sections, 0 code blocks [ai-prompt-engineering-safety-review] ⚠ No code blocks — agents perform better with concrete snippets and commands. [structured-autonomy-generate] 📊 structured-autonomy-generate: 921 BPE tokens [chars/4: 1,033] (detailed ✓), 10 sections, 3 code blocks [structured-autonomy-implement] 📊 structured-autonomy-implement: 209 BPE tokens [chars/4: 272] (compact ✓), 0 sections, 0 code blocks [structured-autonomy-implement] ⚠ No section headers — agents navigate structured documents better. [structured-autonomy-implement] ⚠ No code blocks — agents perform better with concrete snippets and commands. [structured-autonomy-implement] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [structured-autonomy-plan] 📊 structured-autonomy-plan: 677 BPE tokens [chars/4: 759] (detailed ✓), 9 sections, 1 code blocks [swift-mcp-server-generator] 📊 swift-mcp-server-generator: 3,781 BPE tokens [chars/4: 4,374] (standard ~), 30 sections, 18 code blocks [swift-mcp-server-generator] ⚠ Skill is 3,781 BPE tokens (chars/4 estimate: 4,374) — approaching "comprehensive" range where gains diminish. [create-technical-spike] 📊 create-technical-spike: 1,358 BPE tokens [chars/4: 1,643] (detailed ✓), 33 sections, 1 code blocks [ai-prompt-engineering-safety-review] 📊 ai-prompt-engineering-safety-review: 2,185 BPE tokens [chars/4: 2,540] (detailed ✓), 19 sections, 0 code blocks [ai-prompt-engineering-safety-review] ⚠ No code blocks — agents perform better with concrete snippets and commands. [csharp-nunit] 📊 csharp-nunit: 636 BPE tokens [chars/4: 711] (detailed ✓), 8 sections, 0 code blocks [csharp-nunit] ⚠ No code blocks — agents perform better with concrete snippets and commands. [csharp-nunit] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [java-junit] 📊 java-junit: 695 BPE tokens [chars/4: 746] (detailed ✓), 8 sections, 0 code blocks [java-junit] ⚠ No code blocks — agents perform better with concrete snippets and commands. [java-junit] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [playwright-explore-website] 📊 playwright-explore-website: 140 BPE tokens [chars/4: 171] (compact ✓), 2 sections, 0 code blocks [playwright-explore-website] ⚠ Skill is only 140 BPE tokens (chars/4 estimate: 171) — may be too sparse to provide actionable guidance. [playwright-explore-website] ⚠ No code blocks — agents perform better with concrete snippets and commands. [playwright-generate-test] 📊 playwright-generate-test: 178 BPE tokens [chars/4: 220] (compact ✓), 2 sections, 0 code blocks [playwright-generate-test] ⚠ Skill is only 178 BPE tokens (chars/4 estimate: 220) — may be too sparse to provide actionable guidance. [playwright-generate-test] ⚠ No code blocks — agents perform better with concrete snippets and commands. [playwright-generate-test] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [typescript-mcp-server-generator] 📊 typescript-mcp-server-generator: 759 BPE tokens [chars/4: 925] (detailed ✓), 12 sections, 0 code blocks [typescript-mcp-server-generator] ⚠ No code blocks — agents perform better with concrete snippets and commands. [typespec-api-operations] 📊 typespec-api-operations: 2,327 BPE tokens [chars/4: 2,287] (detailed ✓), 35 sections, 16 code blocks [typespec-api-operations] ⚠ No numbered workflow steps — agents follow sequenced procedures more reliably. [typespec-create-agent] 📊 typespec-create-agent: 672 BPE tokens [chars/4: 737] (detailed ✓), 5 sections, 1 code blocks [typespec-create-api-plugin] 📊 typespec-create-api-plugin: 979 BPE tokens [chars/4: 1,013] (detailed ✓), 11 sections, 9 code blocks [winui3-migration-guide] 📊 winui3-migration-guide: 2,196 BPE tokens [chars/4: 2,226] (detailed ✓), 18 sections, 13 code blocks {Ansi.Red}Skill spec conformance failures — fix the errors above.{Ansi.Reset} ❌ Duplicate skill name 'azure-resource-health-diagnose' found in 'plugins/devops-oncall/skills/azure-resource-health-diagnose' (first seen in 'plugins/azure-cloud-development/skills/azure-resource-health-diagnose') ❌ Duplicate skill name 'openapi-to-application-code' found in 'plugins/openapi-to-application-go/skills/openapi-to-application-code' (first seen in 'plugins/openapi-to-application-csharp-dotnet/skills/openapi-to-application-code') ❌ Duplicate skill name 'openapi-to-application-code' found in 'plugins/openapi-to-application-java-spring-boot/skills/openapi-to-application-code' (first seen in 'plugins/openapi-to-application-csharp-dotnet/skills/openapi-to-application-code') ❌ Duplicate skill name 'openapi-to-application-code' found in 'plugins/openapi-to-application-nodejs-nestjs/skills/openapi-to-application-code' (first seen in 'plugins/openapi-to-application-csharp-dotnet/skills/openapi-to-application-code') ❌ Duplicate skill name 'openapi-to-application-code' found in 'plugins/openapi-to-application-python-fastapi/skills/openapi-to-application-code' (first seen in 'plugins/openapi-to-application-csharp-dotnet/skills/openapi-to-application-code') ❌ Duplicate skill name 'create-technical-spike' found in 'plugins/technical-spike/skills/create-technical-spike' (first seen in 'plugins/project-planning/skills/create-technical-spike') ❌ Duplicate skill name 'ai-prompt-engineering-safety-review' found in 'plugins/testing-automation/skills/ai-prompt-engineering-safety-review' (first seen in 'plugins/security-best-practices/skills/ai-prompt-engineering-safety-review') ❌ Duplicate skill name 'csharp-nunit' found in 'plugins/testing-automation/skills/csharp-nunit' (first seen in 'plugins/csharp-dotnet-development/skills/csharp-nunit') ❌ Duplicate skill name 'java-junit' found in 'plugins/testing-automation/skills/java-junit' (first seen in 'plugins/java-development/skills/java-junit') ❌ Duplicate skill name 'playwright-explore-website' found in 'plugins/testing-automation/skills/playwright-explore-website' (first seen in 'plugins/frontend-web-dev/skills/playwright-explore-website') ❌ Duplicate skill name 'playwright-generate-test' found in 'plugins/testing-automation/skills/playwright-generate-test' (first seen in 'plugins/frontend-web-dev/skills/playwright-generate-test') ```
> **Note:** The validator returned a non-zero exit code. Please review the findings above before merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant