Execute secure Git operations and generate markdown commit summaries.
npx skills add https://github.com/joleques/northstar-ai --skill git-ops-joleques
Please help me install this Agent Skill. Skill: git-ops Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/git-ops Command: npx skills add https://github.com/joleques/northstar-ai --skill git-ops-joleques
This Skill standardizes and executes Git operations in a safe, repeatable way so users and agents avoid ad-hoc commands, inconsistent commit messages, and missing human-readable change summaries. It reduces risk by validating repositories, resolving the correct working directory, and gating destructive actions with confirmations.
Run the git-ops skill to stage changes, generate a human-readable git-ops summary file, confirm the standardized commit message (optionally with a ticket), and push the update to the remote.
High-intent search queries and answers about installing and using this skill.
To automate git commit messages and push safely, use a bash shell-script flow that stages changes, generates a markdown summary, and prompts for confirmations before executing destructive actions. This enforces consistent formatting and validates the repository state before pushing.
Yes, you can generate human-readable summaries of git diffs automatically by invoking a bash script that analyzes staged changes and writes a markdown summary file. This summary is then amended into the commit with the generated commit hash.
Yes, you need bash, sed, and git installed in your environment to run these automated git operations. The workflow executes provided bash scripts that rely on these underlying dependencies to resolve directories, format messages, and generate summaries.
The best way to enforce standardized commit messages with a ticket ID is to use an automation flow that prompts for the ticket and message, then formats them into a consistent string. This prevents ad-hoc commands and ensures uniform commit history across a team.
A composite git workflow handles destructive actions like revert and rebase by enforcing confirmation prompts before execution. It validates the repository state and resolves the correct working directory using git -C to ensure operations target the right local repository safely.
You should use shell scripts for local repo management to avoid inconsistent commit messages and missing change summaries. Standardized scripts validate the repository, target the correct directory, and gate destructive actions, reducing the risk of human error associated with manual git commands.
greencmSave project context including git state, decisions, and tasks via shell script.
mattg101Stage all changes, commit with a message, and push to a remote Git repository.
pedronauckRebase Git branches onto main with conflict analysis and resolution strategies.
samChang72Automate git stage, commit, and push operations with conventional commit messages.
