git-flow-branch-creator

Instruções

<instructions>
	<title>Git Flow Branch Creator</title>
	<description>This prompt analyzes your current git changes using git status and git diff (or git diff --cached), then intelligently determines the appropriate branch type according to the Git Flow branching model and creates a semantic branch name.</description>
	<note>
		Just run this prompt and Copilot will analyze your changes and create the appropriate Git Flow branch for you.
	</note>
</instructions>

Fluxo de Trabalho

Siga estes passos:

1. Execute git status para revisar o estado atual do repositório e os arquivos alterados.
2. Execute git diff (para alterações não preparadas) ou git diff --cached (para alterações preparadas) para analisar a natureza das mudanças.
3. Analise as mudanças usando o Framework de Análise de Branches do Git Flow abaixo.
4. Determine o tipo de branch apropriado com base na análise.
5. Gere um nome de branch semântico seguindo as convenções do Git Flow.
6. Crie o branch e mude para ele automaticamente.
7. Forneça um resumo da análise e os próximos passos.

Framework de Análise de Branches do Git Flow

<analysis-framework>
	<branch-types>
		<feature>
			<purpose>New features, enhancements, non-critical improvements</purpose>
			<branch-from>develop</branch-from>
			<merge-to>develop</merge-to>
			<naming>feature/descriptive-name or feature/ticket-number-description</naming>
			<indicators>
				<indicator>New functionality being added</indicator>
				<indicator>UI/UX improvements</indicator>
				<indicator>New API endpoints or methods</indicator>
				<indicator>Database schema additions (non-breaking)</indicator>
				<indicator>New configuration options</indicator>
				<indicator>Performance improvements (non-critical)</indicator>
			</indicators>
		</feature>

		<release>
			<purpose>Release preparation, version bumps, final testing</purpose>
			<branch-from>develop</branch-from>
			<merge-to>develop AND master</merge-to>
			<naming>release-X.Y.Z</naming>
			<indicators>
				<indicator>Version number changes</indicator>
				<indicator>Build configuration updates</indicator>
				<indicator>Documentation finalization</indicator>
				<indicator>Minor bug fixes before release</indicator>
				<indicator>Release notes updates</indicator>
				<indicator>Dependency version locks</indicator>
			</indicators>
		</release>

		<hotfix>
			<purpose>Critical production bug fixes requiring immediate deployment</purpose>
			<branch-from>master</branch-from>
			<merge-to>develop AND master</merge-to>
			<naming>hotfix-X.Y.Z or hotfix/critical-issue-description</naming>
			<indicators>
				<indicator>Security vulnerability fixes</indicator>
				<indicator>Critical production bugs</indicator>
				<indicator>Data corruption fixes</indicator>
				<indicator>Service outage resolution</indicator>
				<indicator>Emergency configuration changes</indicator>
			</indicators>
		</hotfix>
	</branch-types>
</analysis-framework>

Convenções de Nomenclatura de Branches

<naming-conventions>
	<feature-branches>
		<format>feature/[ticket-number-]descriptive-name</format>
		<examples>
			<example>feature/user-authentication</example>
			<example>feature/PROJ-123-shopping-cart</example>
			<example>feature/api-rate-limiting</example>
			<example>feature/dashboard-redesign</example>
		</examples>
	</feature-branches>

	<release-branches>
		<format>release-X.Y.Z</format>
		<examples>
			<example>release-1.2.0</example>
			<example>release-2.1.0</example>
			<example>release-1.0.0</example>
		</examples>
	</release-branches>

	<hotfix-branches>
		<format>hotfix-X.Y.Z OR hotfix/critical-description</format>
		<examples>
			<example>hotfix-1.2.1</example>
			<example>hotfix/security-patch</example>
			<example>hotfix/payment-gateway-fix</example>
			<example>hotfix-2.1.1</example>
		</examples>
	</hotfix-branches>
</naming-conventions>

Processo de Análise

<analysis-process>
	<step-1>
		<title>Análise da Natureza da Mudança</title>
		<description>Examine os tipos de arquivos modificados e a natureza das mudanças</description>
		<criteria>
			<files-modified>Observe as extensões dos arquivos, a estrutura de diretórios e o propósito</files-modified>
			<change-scope>Determine se as mudanças são aditivas, corretivas ou preparatórias</change-scope>
			<urgency-level>Avalie se as mudanças abordam problemas críticos ou são de desenvolvimento</urgency-level>
		</criteria>
	</step-1>

	<step-2>
		<title>Classificação do Git Flow</title>
		<description>Mapeie as mudanças para o tipo de branch apropriado do Git Flow</description>

…