Skill

git-workflow

Git workflow fundamentals: branching strategy, commit conventions, PR workflow, conflict resolution, release tagging. Foundation for parallel-workflow. [EXPLICIT] Trigger: "git workflow", "branching", "commit convention", "PR process", "merge conflict", "release"

From jm-adk

Install

Run in your terminal

npx claudepluginhub javimontano/jm-adk-alfa

Tool Access

This skill is limited to using the following tools:

ReadWriteGlobGrepBash

Supporting Assets

View in Repository

agents/guardian.md

agents/lead.md

agents/specialist.md

agents/support.md

evals/evals.json

knowledge/body-of-knowledge.md

knowledge/knowledge-graph.md

prompts/meta.md

prompts/primary.md

prompts/variations/deep.md

prompts/variations/quick.md

templates/output.docx.md

templates/output.html

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

agent-introspection-debugging

Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.

everything-claude-code

142.9k

Stats

Stars1

Forks0

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

Procedure

Step 1: Discover

Read existing code and identify current patterns

Check for existing documentation or configuration

Identify gaps and improvement opportunities

Step 2: Analyze

Evaluate options and select the best approach for the project context

Consider Constitution principles (XIII Think First, XIV Simple First)

Map to quality gates

Step 3: Execute

Implement the solution following established patterns

Apply evidence tags to all claims

Generate output using brand template if HTML

Step 4: Validate

Verify implementation works correctly

Check against quality criteria

Evidence tags applied to all claims

Scenario

Handling

Empty or minimal input

Request clarification before proceeding

Conflicting requirements

Flag conflicts explicitly, propose resolution

Out-of-scope request

Redirect to appropriate skill or escalate

Git Workflow

"Method over hacks. Evidence over assumption."

TL;DR

Establishes Git workflow fundamentals: branching strategy (trunk-based or feature branches), conventional commit messages, PR templates and review process, conflict resolution patterns, and release tagging with semantic versioning. Foundation that parallel-workflow builds on. [EXPLICIT]

Procedure

Step 1: Discover

Read existing code and identify current patterns
Check for existing documentation or configuration
Identify gaps and improvement opportunities

Step 2: Analyze

Evaluate options and select the best approach for the project context
Consider Constitution principles (XIII Think First, XIV Simple First)
Map to quality gates

Step 3: Execute

Implement the solution following established patterns
Apply evidence tags to all claims
Generate output using brand template if HTML

Step 4: Validate

Verify implementation works correctly
Check against quality criteria
Evidence tags applied to all claims

Quality Criteria

Implementation follows established patterns
Evidence tags applied to all claims
Tested and verified
Constitution-compliant

Related Skills

parallel-workflow — Advanced parallel Git patterns
github-actions-ci — CI/CD integration
deployment-checklist — Pre-deploy Git checks

Usage

Example invocations:

"/git-workflow" — Run the full git workflow workflow
"git workflow on this project" — Apply to current context

Assumptions & Limits

Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
Requires English-language output unless otherwise specified [EXPLICIT]
Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate