skills.rest
clfigueiredo
clfigueiredoCOMMUNITY
Explore all skills by this author →
GitHub

github-workflow-student

Guides GitHub workflows for repositories, branches, commits, pull requests, and basic CI.

5|15|Updated Jul 8, 2026
Search Tags:#git#version control#pull request#commit#github#branching#ci
One-click install
npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill github-workflow-student-clfigueiredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-workflow-student
Source: https://github.com/clfigueiredo/hermes-infra-skills/tree/main/.hermes/skills/curso-hermes/github-workflow-student
Command: npx skills add https://github.com/clfigueiredo/hermes-infra-skills --skill github-workflow-student-clfigueiredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Students and beginners often struggle with safe Git and GitHub practices, risking leaked secrets, messy commits, and broken shared branches when working on study projects and MVPs. ## Core Features & Use Cases - Repository and Branch Workflow: Provides a simple command sequence for creating feature branches, committing, and pushing changes. - Commit and PR Quality Checklists: Enforces pre-commit checks like reviewing diffs, avoiding secrets in files, and writing clear PR descriptions with test evidence. - Common Mistake Prevention: Warns against committing .env files, mixing refactors with features, and force-pushing shared branches. - Use Case: A student finishing a new feature can follow the guided flow to create a branch, commit with a clean message, push, and open a well-structured pull request via gh pr create. ## Quick Start Ask the assistant to guide you through creating a feature branch, committing your changes safely, and opening a pull request on GitHub.

Frequently Asked Questions about github-workflow-student

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

FAQPage Schema
How do I create a feature branch and open a pull request on GitHub?▼

Create a branch with git checkout -b feat/my-feature, commit your changes with a clear message, push with git push -u origin, then open a PR on GitHub or run gh pr create if the GitHub CLI is authenticated.

What should I check before committing code to Git?▼

Review your changes with git diff, confirm no secrets or .env files are included, run builds or tests when possible, and write a short, clear commit message describing a single change.

How do I write a good pull request description?▼

Structure the PR with three sections: what changed, how to test it, and evidence such as commands, screenshots, or logs. This gives reviewers the context needed to evaluate the change quickly.

Why is force pushing to a shared branch a problem?▼

Force pushing rewrites shared history, which can erase teammates' commits and cause conflicts. Only force push on your own branches, and always warn collaborators before doing it on shared work.

What common Git mistakes should beginners avoid?▼

Avoid committing .env files with secrets, making giant commits without a single theme, mixing refactors with features, and force pushing shared branches without warning. Each mistake makes review and rollback harder.

Related Skills

Explore More Software Engineering Skills→
alexaundrealexaundre

yeet

Stage, commit, push, and open a GitHub pull request via the GitHub CLI.

Community
Intermediate
lengo0951lengo0951

ck:ship

Automate code release pipelines with a single command.

Community
Advanced
azmiariffarisazmiariffaris

requesting-code-review

Automate pre-commit verification with static security scans and quality gates.

Community
Advanced
ClaudioCeppi83ClaudioCeppi83

spotify-player

Control Spotify playback and search tracks from the terminal.

Community
Intermediate