Elifarley C. avatar

Elifarley C.

Community

@elifarley

91Followers
|
140Public Repos
|
3Published Skills

🇧🇷🇺🇾🇩🇪🇫🇷

Skills Distribution
DomainDeveloper To...Version Control Op.. (45%)Git Worktree Manag.. (25%)Repository Forensi.. (20%)Branch & Commit Li.. (10%)

Agent Skills by Elifarley C.

Showing 3 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Elifarley C.

FAQPage Schema
What tasks can I perform with Elifarley C.'s Hug SCM skills?

You can manage all Git operations through Hug: committing and amending changes, staging and unstaging files, viewing history and diffs, inspecting repository state, creating worktrees for branch-worthy work, and performing expert-level repository analysis to trace bugs and code evolution.

Who are these Hug SCM skills designed for?

They target software developers and engineers who work heavily in Git repositories and want an enhanced Git replacement. They suit anyone handling feature branches, bugfixes, refactors, multi-step tasks, or deep investigation of code history and change provenance.

How do the Hug skills run in practice?

The skills execute through Bash, with hug-workflow restricted to Bash(hug:*) commands. Invoke hug-worktree with a new branch name or task description to start isolated work, hug-workflow for commits and staging, and hug-repo-analysis for repository investigation.

What are the prerequisites for using these skills?

You need a Git repository and Bash access, since all three skills run shell commands. The hug-workflow skill specifically requires the Hug enhanced Git replacement to be available, as its allowed commands are scoped to hug:* invocations.

When should I use hug-worktree versus hug-workflow?

Use hug-worktree at the start of any branch-worthy work—features, bugfixes, refactors, or spec documents—to create an isolated worktree first. Use hug-workflow afterward for ongoing operations like committing, amending, staging, viewing logs, and inspecting repository state.