CtrlK
BlogDocsLog inGet started
Tessl Logo

workflow-run-tag-resolution

Resolve release tags reliably in follow-on GitHub workflows when the source repo uses annotated tags.

71

Quality

65%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.squad/skills/workflow-run-tag-resolution/SKILL.md
SKILL.md
Quality
Evals
Security

Context

Use this when a GitHub Actions workflow is triggered by workflow_run and needs to recover the release tag or version from the completed source workflow.

Patterns

  1. Check out the source repository with tags before resolving the version.
  2. Resolve the tag from the local git graph, not from git/matching-refs, when the repo uses annotated tags.
  3. Use git tag --points-at "$HEAD_SHA" and sort/filter for semver-style release tags.
  4. Add a short retry loop to absorb brief tag-visibility delays after the upstream workflow completes.
  5. Keep manual replay paths explicit and separately validated.

Examples

  • Good: actions/checkout@v4 with fetch-depth: 0, then git fetch --force --tags origin and git tag --points-at "$HEAD_SHA" --sort=-version:refname.
  • Bad: comparing workflow_run.head_sha directly to the REST matching-refs .object.sha value for annotated tags.

Anti-Patterns

  • Assuming release tags are lightweight tags.
  • Resolving the "latest release" instead of the tag that points at the triggering commit.
  • Treating an empty tag lookup as proof the release failed before checking whether the lookup method understands annotated tags.
Repository
sbroenne/mcp-server-excel
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.