hug-workflow

Translates Git operations into Hug commands for commits, staging, and repository inspection.

2|1|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/elifarley/hug-scm --skill hug-workflow-elifarley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hug-workflow
Source: https://github.com/elifarley/hug-scm/tree/main/docs/skills/hug-workflow
Command: npx skills add https://github.com/elifarley/hug-scm --skill hug-workflow-elifarley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Git commands are complex and error-prone, especially for staging, amending commits, and inspecting repository state. This Skill replaces raw Git with Hug, a humane Git interface that provides safer, more memorable commands with built-in guards against common mistakes like accidental amends or staging unintended files. ## Core Features & Use Cases - Safe Commit Workflows: Enforces a staging decision tree (hug sla, hug a, hug sls, hug c) so only intended files are committed, with support for multi-line commit messages via heredoc. - Commit Fixing: Amend commit messages or add/remove files from the last commit using hug cmod and hug back, with safety guards against content-null amends. - Repository Inspection: View staged/unstaged/untracked files, outgoing commits, and search history by message or code change. - Use Case: After editing several files, ask the AI to commit only the relevant changes. It runs hug sla to review all modifications, stages only the intended files, verifies with hug sls, and commits with a properly formatted message. ## Quick Start Ask the AI to review all uncommitted changes and commit only the files related to your current task using Hug.

Frequently Asked Questions about hug-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit only specific files with Hug?

Run hug sla to list all staged, unstaged, and untracked files, then stage specific files with hug a <file1> <file2>. Verify the staged set with hug sls, then commit using hug c -m 'message'.

How do I amend a Git commit message without changing files?

First run hug sls to confirm no files are staged, then run hug cmod -m 'new message'. This amends only the message while keeping the commit's file contents intact.

What is the Hug equivalent of git diff --cached?

Use hug ss to show staged changes along with file stats. For unstaged changes use hug su, and for all working directory changes use hug sw.

Why does hug cmod refuse to amend my commit?

The cmod and cmoda commands refuse content-null amends and exit with code 3 as a safety guard. Stage files first or pass a message with -m; use -f only for a deliberate re-hash or re-date.

How do I write a multi-line commit message with Hug?

Use hug c -F - with a heredoc to pipe a multi-line message from stdin. This avoids fragile nested quoting patterns while preserving natural formatting with sections like WHY, WHAT, and IMPACT.