Stats
Actions
Tags
From git-intent-interface
On-demand knowledge about the git-intent methodology. This skill should be used when the user asks about "git intent workflow", "!! markers", "how to use git-intent", "marker syntax", "commit message protocol", or "how does git intent work".
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-intent-interface:g-intent-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A workflow where git is the instruction interface between human and agent. The human delivers intent through channels: **commit messages**, inline **`!!` markers** in any file type, and in the chat. The agent reads the diff, executes the instructions, and commits the results.
A workflow where git is the instruction interface between human and agent. The human delivers intent through channels: commit messages, inline !! markers in any file type, and in the chat. The agent reads the diff, executes the instructions, and commits the results.
The main goal is to preserve intent for future LLM sessions, so all commit messages by agents must include motivation.
We rely heavily on git — every change is a commit the human can review, revert, or amend. When in doubt, the agent should make the change and commit rather than ask for confirmation. Git is the review interface.
All skills are in the initial prototyping phase — this is guidance, not strict rules. We are inventing mechanics along the way.
!! — process all markers in the committed files, no additional instruction!! instruction text — process markers AND apply the instruction globally to committed files!!) with !! markers in files — the commit message is context/explanation, markers are the instructions!! check consistency, !! add error handling)!! markers in files — specific actions tied to a location in the fileBoth are ephemeral by default — commit messages are read and executed, markers are removed after processing.
Markers use the native comment syntax of each language, prefixed with !!. They are always single-line. Place the marker on the line above or beside the target code.
Default: all !! markers are removed after the agent processes them.
Exception: a marker containing [keep] is preserved:
#!! [keep] revisit after v2
def legacy_handler():
...
The [keep] keyword itself stays in the marker. The user removes it manually when ready.
Subject = what changed, body = why. Diff shows how.
!! markers as inline instructions where neededgit commit — the commit message is either !! (just process markers) or !! additional instruction/g-intent-apply N/git-log-patches N or git log -p/g-intent-apply N — process last N commits as instructions/g-intent-squash-archive — squash all branch commits, preserve history in a git tag/git-log-patches N — show git log -p --reverse for last N commitsnpx claudepluginhub maxim-uvarov/my-claude-skills --plugin git-intent-interfaceManages Git commit workflow using Conventional Commits format with safety protocols. Creates, validates, executes commits; handles hooks, PRs, and safety checks before operations.
Crafts structured Git commit messages with type-prefixed subjects (feat, fix), explanatory bodies on why changes were made, and footers for issues or breaks, acting as code documentation.
Structures git workflow practices for committing, branching, resolving conflicts, and organizing work across parallel streams. Use when making any code change.