harmont-cli: Skill for Claude Code

Convert existing GitHub Actions workflows (.github/workflows/*.yml / *.yaml) into Harmont CI pipelines. This skill reads your GHA configuration, explains what maps directly and what changes, then uses the write-pipeline skill to produce the Harmont pipeline.

When to use

• The user asks to "convert", "migrate", or "port" their GitHub Actions to Harmont
• The user says "I have GHA workflows" and wants Harmont equivalents
• The user asks "how do I replace GitHub Actions with Harmont"
• hm init told the user about this skill after detecting .github/workflows/

When NOT to use

• The user wants to write a Harmont pipeline from scratch — use the write-pipeline skill directly
• The user wants to keep using GitHub Actions alongside Harmont (dual CI setup)
• The user is debugging an existing Harmont pipeline — use the validate-ci skill

Before you start

1. Read every workflow file in .github/workflows/:

   find .github/workflows -name '*.yml' -o -name '*.yaml' | sort
   

   Read each file. Understand what each workflow does, what triggers it, and what its jobs and steps accomplish.

2. Fetch the Harmont patterns guide — required before writing anything:

   WebFetch https://docs.harmont.dev/pipeline-sdk/patterns.md
   

Procedure

1. Inventory the GHA workflows. For each .yml file, note:

   • Workflow name and trigger events (on: push, on: pull_request, etc.; note any on: schedule — see the mapping table for why scheduled triggers don't map to a local pipeline)
   • Each job: its name, runs-on, and what it does
   • Dependencies between jobs (needs:)
   • Services used (services:)
   • Secrets and environment variables referenced
   • Caching steps (actions/cache, actions/setup-* with built-in caching)
   • Artifacts (actions/upload-artifact, actions/download-artifact)
   • Matrix strategies

2. Map GHA concepts to Harmont. Present the user with a summary table covering what they have and how it translates: