git-workflow

النجوم١٠

التفرعات٢

آخر تحديث١٨ مايو ٢٠٢٦ في ٠٧:٠٢

Git workflow management — use when the user mentions git, conventional commits, commit quality, branch management, worktree operations, GitFlow, changelog generation, semantic versioning, release notes, backlog management, or issue tracking integration. NOT for CI/CD pipelines or pipeline YAML (use cicd-pipelines), NOT for non-git workflow orchestration (use skillstack-workflows or multi-agent-patterns), NOT for code review content or PR quality assessment (use code-review).

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

viktorbezdek

viktorbezdek/skillstack

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

30 ملفات

SKILL.md

readonly

المزيد من هذا المستودع

نفس المستودع

cloud-infrastructure

viktorbezdek/skillstack

Cloud infrastructure design and infrastructure-as-code (IaC) authoring. Use for Terraform module authoring, AWS CDK constructs, cloud architecture design (VPCs, load balancers, managed services, serverless), multi-region and disaster-recovery patterns, cost-optimisation analysis, and IaC code review. Trigger phrases: "write Terraform for", "design the AWS architecture", "set up a VPC", "convert this to CDK", "optimise our cloud costs". NOT for application-layer code — this skill models infrastructure, not the code running on it. NOT for Kubernetes application manifests (Deployments, Services, Ingress) — those belong in a k8s-specific skill. NOT for CI/CD pipeline configuration — that is a deployment concern separate from infrastructure provisioning.

2026-06-0510

competitive-intelligence

viktorbezdek/skillstack

Competitive intelligence and market positioning analysis for product and GTM decisions. Use for competitor landscape mapping, positioning gap identification, win/loss pattern synthesis, battlecard creation, market-sizing estimates (TAM/SAM/SOM), and differentiation analysis. Trigger phrases: "map the competitive landscape", "create a battlecard for", "analyse our win/loss patterns", "how do we differentiate from", "size this market". NOT for primary market research (customer interviews, surveys) — this skill works from existing public and internal data. NOT for financial modelling or investor decks — competitive context informs the story but this skill does not build financial projections. NOT for pricing strategy deep-dives — pricing has its own set of constraints and frameworks beyond competitive positioning.

2026-06-0510

database-design

viktorbezdek/skillstack

Database design and schema engineering for relational databases. Use for SQL schema design, ORM model authoring, migration strategies (Alembic, Liquibase, Flyway, Drizzle), query optimisation, indexing decisions, normalisation vs denormalisation trade-offs, and data-integrity constraints. Trigger phrases: "design this schema", "write a migration", "optimise this query", "model these entities", "add an index". NOT for NoSQL/document stores — use a dedicated NoSQL skill for those. NOT for ETL pipelines or data warehousing at scale — those involve different trade-offs. NOT for ORM configuration (framework setup) — this skill is about DATA SHAPE, not connection pooling or ORM bootstrap.

2026-06-0510

email-marketing

viktorbezdek/skillstack

Email content writing for newsletters, drip sequences, onboarding flows, and transactional emails. Use for newsletter drafting, automated drip sequence copy, welcome email series, subject line and preview text optimisation, re-engagement emails, and plain-language transactional email (receipts, confirmations, alerts). Trigger phrases: "write a newsletter", "draft an onboarding email sequence", "write a subject line", "write a drip campaign", "create a welcome email". NOT for email infrastructure setup (ESP config, sending domains, DKIM/DMARC) — that is a technical ops concern. NOT for social media content — use the social-media-content skill for LinkedIn or Twitter. NOT for cold outreach / sales prospecting emails — those have compliance and conversion constraints beyond marketing content.

2026-06-0510

research-synthesis

viktorbezdek/skillstack

Structured research and evidence synthesis for knowledge-intensive tasks. Use for multi-source research coordination, evidence triangulation across conflicting sources, competing-hypothesis analysis, literature/documentation sweeps, claim verification, and synthesis reports. Trigger phrases: "research this topic", "synthesise findings from", "compare sources on", "what does the evidence say about", "triangulate these claims". NOT for primary data collection (interviews, surveys) — this skill synthesises existing sources. NOT for code research or codebase exploration — use CodeGraph and Semble for that. NOT for creative content generation — synthesis produces structured analysis, not narrative content.

2026-06-0510

security-engineering

viktorbezdek/skillstack

Application security design and threat-informed engineering. Use for authentication and authorisation architecture (OAuth2, JWT, RBAC, ABAC), OWASP Top 10 vulnerability analysis, secrets management (Vault, AWS Secrets Manager, environment isolation), input validation patterns, secure API design, SQL injection and XSS prevention, and security-aware code review. Trigger phrases: "secure this endpoint", "design an auth system", "review this for security vulnerabilities", "how do I store secrets", "implement RBAC". NOT for network/infrastructure security (firewalls, VPNs, WAF config) — those belong in cloud-infrastructure. NOT for compliance auditing (SOC2, GDPR gap assessments) — that requires a compliance specialist. NOT for penetration testing or red-teaming — this skill is for defensive engineering, not offensive exercises.

2026-06-0510

name	git-workflow
description	Git workflow management — use when the user mentions git, conventional commits, commit quality, branch management, worktree operations, GitFlow, changelog generation, semantic versioning, release notes, backlog management, or issue tracking integration. NOT for CI/CD pipelines or pipeline YAML (use cicd-pipelines), NOT for non-git workflow orchestration (use skillstack-workflows or multi-agent-patterns), NOT for code review content or PR quality assessment (use code-review).
allowed-tools	Bash, Read, Grep, Glob, Write

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting, whitespace
`refactor`	Code change without behavior change
`perf`	Performance improvement
`test`	Adding or correcting tests
`chore`	Build/tooling changes
`ci`	CI/CD changes
`build`	Build system/dependencies
`revert`	Reverts a previous commit

Size	LOC	Action
Tiny	< 10	Single logical change
Small	10-50	Typical atomic commit
Medium	50-200	Feature component
Large	200-500	Consider splitting
Too Large	> 500	Definitely split

Command	Action
`/commit`	Smart commit helper with auto-analysis
`/validate <msg>`	Validate commit message format
`/types`	Show all commit types
`/scopes`	Explain scopes with examples
`/breaking`	Breaking change guide
`/changelog`	Generate changelog from commits
`/version`	Determine next semantic version
`/examples`	Show commit examples
`/fix`	Help amend/fix last commit

Type	Pattern	Purpose
Feature	`feature/{name}`	New features
Fix	`fix/{name}`	Bug fixes
Hotfix	`hotfix/{name}`	Critical production fixes
Release	`release/{version}`	Release preparation

Command	Action
"Update story tree"	Run full workflow
"Show story tree"	Visualize current tree
"Tree status"	Show metrics only
"Set capacity for [id] to [N]"	Adjust capacity
"Mark [id] as [status]"	Change status
"Generate stories for [id]"	Force generation
"Initialize story tree"	Create new database

Status	Symbol	Meaning
concept	.	Idea, not approved
approved	v	Human approved
epic	E	Needs decomposition
planned	o	Plan created
in-progress	D	Partially complete
implemented	+	Complete/done
ready	#	Production ready

Anti-Pattern	Problem	Solution
Dumping all changes in one commit	Un-reviewable, un-revertable; hides logical changes	Group by scope/type using `group-files.py`; one logical change per commit
Vague commit messages ("wip", "fix stuff", "updates")	Cannot generate changelog; bisect useless	Use conventional commits: type(scope): imperative subject
Non-imperative subject ("added feature")	Inconsistent with conventional commits; reads as past tense	Use imperative mood: "add feature" not "added feature"
Missing issue references	No link between code and requirements; lost knowledge	Include `Closes #N` or `Refs #N` in commit footer
Commit too large (>500 LOC)	Too much surface area for review; hard to revert independently	Split into atomic commits; group-files.py suggests groupings
Mixing concerns in one commit (impl + tests + docs)	Hard to revert just tests or just docs; bloats review	Separate: feat commit, test commit, docs commit
Breaking change without `BREAKING CHANGE:` footer	Changelog misses breaking changes; version bump wrong	Always document breaking changes in footer; triggers major version
Working on main instead of feature branch	No isolation; hard to revert; messy history	Use GitFlow: feature/ for new work, fix/ for bugs, hotfix/ for prod
Stashing instead of worktrees	Lost context; stash conflicts; no parallel work	Use `git worktree` for parallel feature development
Missing changelog before release	Manual, incomplete release notes	Run `changelog.py` auto-generated from conventional commits
Guessing version number	Incorrect semver; surprises in release	Run `version.py` -- auto-calculated from commit types

Script	Purpose
`analyze-diff.py`	Analyze staged changes, suggest commits
`validate.py`	Validate commit message format
`changelog.py`	Generate changelog from commits
`version.py`	Calculate next semantic version
`commit-analyzer.py`	Full commit quality analysis
`conventional-commits.py`	Conventional commits helper
`group-files.py`	Intelligent file grouping
`issue-tracker.py`	Issue sync and detection

Script	Purpose
`create_worktree.sh`	Create worktree with GitFlow conventions
`list_worktrees.sh`	List all worktrees with status
`cleanup_worktrees.sh`	Clean up merged/stale worktrees
`init-environment.py`	Initialize GitHub workflow environment

Issue	Recovery
Empty commit message	Generate from changes
No staged changes	Prompt to stage
Format violations	Suggest correction
Missing issue reference	Search and suggest
Commit too large	Recommend splitting
Database not found	Initialize first
Checkpoint rebased	Run full scan

git-workflow

المزيد من هذا المستودع

المزيد من هذا المستودع

Git Workflow - Comprehensive Git Management Skill

When to Use / Not Use

Decision Tree

Part 1: Commit Management

Conventional Commits Format

Commit Quality Standards

Slash Commands

Intelligent File Grouping

Issue Integration

Part 2: Branch & Worktree Management

GitFlow Branch Conventions

Worktree Operations

Part 3: Release Management

Changelog Generation

Semantic Versioning

Part 4: Story Tree Management

Purpose

Database

Story Format

Workflow Commands

Tree Visualization

Anti-Patterns

Scripts Reference

Commit Scripts

Workflow Scripts

Story Tree Scripts

References

Commit References

Workflow References

Story Tree References

Assets

Integration Points

With Issue Tracking

With PR Reviews

With CI/CD

Error Handling

Source Skills

Git Workflow - Comprehensive Git Management Skill

When to Use / Not Use

Decision Tree

Part 1: Commit Management

Conventional Commits Format

Commit Quality Standards

Slash Commands

Intelligent File Grouping

Issue Integration

Part 2: Branch & Worktree Management

GitFlow Branch Conventions

Worktree Operations

Part 3: Release Management

Changelog Generation

Semantic Versioning

Part 4: Story Tree Management

Purpose

Database

Story Format

Workflow Commands

Tree Visualization

Anti-Patterns

Scripts Reference

Commit Scripts

Workflow Scripts

Story Tree Scripts

References

Commit References

Workflow References

Story Tree References

Assets

Integration Points

With Issue Tracking

With PR Reviews

With CI/CD

Error Handling

Source Skills