@elsikora/git-branch-lint 1.2.1 → 1.2.2-dev.1

package/LICENSE.md

@@ -2,20 +2,8 @@ The MIT License (MIT)
 
 Copyright (c) 2022 Bogdan Kolesnyk (bogdan.kolesnyk@gmail.com)
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/README.md

@@ -1,83 +1,66 @@
 <p align="center">
-  <img src="https://6jft62zmy9nx2oea.public.blob.vercel-storage.com/git-branch-lint-myXi2xH8jqeEIqScu1S9NymOOJVD9I.png" width="500" alt="project-logo">
+  <img src="https://6jft62zmy9nx2oea.public.blob.vercel-storage.com/git-branch-lint-myXi2xH8jqeEIqScu1S9NymOOJVD9I.png" width="500" alt="project-logo" />
 </p>
 
-<h1 align="center">🌿 Git-Branch-Lint</h1>
-<p align="center"><em>Enforce consistent Git branch naming conventions with style and ease</em></p>
+<h1 align="center">Git-Branch-Lint</h1>
+<p align="center"><em>CLI tool for consistent, enforceable Git branch naming.</em></p>
 
-<p align="center">
-    <a aria-label="ElsiKora logo" href="https://elsikora.com">
-  <img src="https://img.shields.io/badge/MADE%20BY%20ElsiKora-333333.svg?style=for-the-badge" alt="ElsiKora">
-</a> <img src="https://img.shields.io/badge/TypeScript-3178C6.svg?style=for-the-badge&logo=typescript&logoColor=white" alt="TypeScript"> <img src="https://img.shields.io/badge/Node.js-339933.svg?style=for-the-badge&logo=node.js&logoColor=white" alt="Node.js"> <img src="https://img.shields.io/badge/npm-CB3837.svg?style=for-the-badge&logo=npm&logoColor=white" alt="npm"> <img src="https://img.shields.io/badge/ESLint-4B32C3.svg?style=for-the-badge&logo=eslint&logoColor=white" alt="ESLint"> <img src="https://img.shields.io/badge/Prettier-F7B93E.svg?style=for-the-badge&logo=prettier&logoColor=black" alt="Prettier"> <img src="https://img.shields.io/badge/Vitest-6E9F18.svg?style=for-the-badge&logo=vitest&logoColor=white" alt="Vitest"> <img src="https://img.shields.io/badge/Rollup-EC4A3F.svg?style=for-the-badge&logo=rollup&logoColor=white" alt="Rollup"> <img src="https://img.shields.io/badge/Git-F05032.svg?style=for-the-badge&logo=git&logoColor=white" alt="Git"> <img src="https://img.shields.io/badge/GitHub%20Actions-2088FF.svg?style=for-the-badge&logo=github-actions&logoColor=white" alt="GitHub Actions">
-</p>
+## Table Of Contents
 
+- [Description](#description)
+- [Features](#features)
+- [Installation](#installation)
+- [Usage](#usage)
+- [Configuration](#configuration)
+- [Clean Architecture Rules](#clean-architecture-rules)
+- [Development](#development)
+- [License](#license)
 
-## 📚 Table of Contents
-- [Description](#-description)
-- [Features](#-features)
-- [Installation](#-installation)
-- [Usage](#-usage)
-- [Roadmap](#-roadmap)
-- [FAQ](#-faq)
-- [License](#-license)
+## Description
 
+`@elsikora/git-branch-lint` validates branch names against team rules and includes an interactive branch-creation flow.
 
-## 📖 Description
-Git-Branch-Lint is a powerful, TypeScript-based CLI tool that brings order to your Git workflow by enforcing consistent branch naming conventions across your entire development team. Built with clean architecture principles, it not only validates branch names but also provides an interactive branch creation wizard that guides developers through creating properly formatted branches. Whether you're managing a small project or a large enterprise codebase, Git-Branch-Lint helps maintain a clean, organized repository structure that makes tracking features, fixes, and releases effortless. It seamlessly integrates with Git hooks, CI/CD pipelines, and supports multiple configuration formats, making it the perfect addition to any modern development workflow.
+The project follows layered clean architecture:
 
-## 🚀 Features
-- ✨ **🎯 **Smart Pattern Matching** - Define flexible branch naming patterns using simple placeholders like `:type/:name` that automatically validate against your configured branch types**
-- ✨ **🚀 **Interactive Branch Creation** - Built-in wizard guides you through creating branches with beautiful prompts, ensuring compliance before the branch is even created**
-- ✨ **🛡️ **Prohibited Branch Protection** - Prevent accidental use of protected branch names like 'main', 'master', or any custom prohibited names you define**
-- ✨ **📏 **Length Validation** - Set minimum and maximum length constraints to keep branch names concise and meaningful**
-- ✨ **🎨 **Beautiful CLI Output** - Colored terminal output with helpful error messages and hints that guide developers to fix issues quickly**
-- ✨ **⚙️ **Flexible Configuration** - Support for multiple config formats (JS, TS, JSON, YAML) with intelligent config discovery via cosmiconfig**
-- ✨ **🔄 **Git Hooks Ready** - Seamlessly integrate with Husky, lint-staged, or any Git hook manager for automatic validation**
-- ✨ **📦 **Zero Config Option** - Works out of the box with sensible defaults while allowing complete customization when needed**
-- ✨ **🏗️ **Clean Architecture** - Built with Domain-Driven Design principles, making the codebase maintainable and extensible**
+- `domain` - business rules, entities, policies, contracts
+- `application` - use cases and orchestration logic
+- `infrastructure` - adapters (git, config loading)
+- `presentation` - CLI controllers, prompts, formatters
 
-## 🛠 Installation
-```bash
-## 📦 Installation
+## Features
+
+- Template-driven branch validation using placeholders (for example `:type/:name` or `:scope/:type/:description`).
+- Optional ticket-id support with pattern `:type/:ticket-:name` (ticket part can be omitted).
+- Interactive branch creation command (`-b` / `--branch`) built directly from configured placeholders.
+- Branch constraints: prohibited names, min/max length, subject regex.
+- Helpful CLI error/hint formatting.
+- Cosmiconfig-based configuration discovery.
 
-Install Git-Branch-Lint as a development dependency in your project:
+## Installation
 
+Install as a dev dependency:
 
-# Using npm
+```bash
 npm install --save-dev @elsikora/git-branch-lint
+```
 
-# Using yarn
-yarn add -D @elsikora/git-branch-lint
+Or with other package managers:
 
-# Using pnpm
+```bash
+yarn add -D @elsikora/git-branch-lint
 pnpm add -D @elsikora/git-branch-lint
-
-# Using bun
 bun add -d @elsikora/git-branch-lint
-
-
-### Global Installation
-
-For system-wide usage across multiple projects:
-
-
-npm install -g @elsikora/git-branch-lint
 ```
 
-## 💡 Usage
-## 🚀 Usage
+## Usage
 
-### Basic Branch Validation
-
-Validate your current Git branch name:
+Validate current branch:
 
 ```bash
 npx @elsikora/git-branch-lint
 ```
 
-### Interactive Branch Creation
-
-Create a new branch with the interactive wizard:
+Start interactive branch creation:
 
 ```bash
 npx @elsikora/git-branch-lint -b
@@ -85,223 +68,130 @@ npx @elsikora/git-branch-lint -b
 npx @elsikora/git-branch-lint --branch
 ```
 
-### Configuration
-
-Git-Branch-Lint uses [cosmiconfig](https://github.com/davidtheclark/cosmiconfig) for configuration file discovery. Create any of these files:
-
-#### JavaScript Configuration (`.elsikora/git-branch-lint.config.js`)
-
-```javascript
-export default {
-  branches: {
-    feature: { 
-      title: "Feature", 
-      description: "🆕 New functionality" 
-    },
-    bugfix: { 
-      title: "Bugfix", 
-      description: "🐛 Bug fixes" 
-    },
-    hotfix: { 
-      title: "Hotfix", 
-      description: "🚑 Urgent production fixes" 
-    },
-    release: { 
-      title: "Release", 
-      description: "📦 Release preparation" 
-    },
-    chore: { 
-      title: "Chore", 
-      description: "🔧 Maintenance tasks" 
-    }
-  },
-  ignore: ["dev", "develop", "staging"],
-  rules: {
-    "branch-pattern": ":type/:name",
-    "branch-subject-pattern": "[a-z0-9-]+",
-    "branch-prohibited": ["main", "master", "prod"],
-    "branch-min-length": 5,
-    "branch-max-length": 60
-  }
-};
-```
-
-#### TypeScript Configuration (`.elsikora/git-branch-lint.config.ts`)
-
-```typescript
-import type { IBranchLintConfig } from '@elsikora/git-branch-lint';
-
-const config: IBranchLintConfig = {
-  branches: {
-    feat: { title: "Feature", description: "✨ New features" },
-    fix: { title: "Fix", description: "🐛 Bug fixes" },
-    docs: { title: "Docs", description: "📚 Documentation" },
-    style: { title: "Style", description: "💄 Styling" },
-    refactor: { title: "Refactor", description: "♻️ Code refactoring" },
-    perf: { title: "Performance", description: "⚡ Performance improvements" },
-    test: { title: "Test", description: "✅ Testing" },
-    build: { title: "Build", description: "📦 Build system" },
-    ci: { title: "CI", description: "👷 CI/CD" }
-  },
-  rules: {
-    "branch-pattern": ":type/:name",
-    "branch-subject-pattern": "[a-z0-9-]+",
-    "branch-min-length": 8,
-    "branch-max-length": 72
-  }
-};
-
-export default config;
-```
-
-#### Package.json Configuration
+Behavior notes:
 
-```json
-{
-  "elsikora": {
-    "git-branch-lint": {
-      "branches": ["feature", "bugfix", "hotfix"],
-      "rules": {
-        "branch-pattern": ":type/:name",
-        "branch-prohibited": ["main", "master"]
-      }
-    }
-  }
-}
-```
+- When `:ticket` is present in `branch-pattern`, both forms are valid:
+  - with ticket: `feature/proj-123-user-authentication`
+  - without ticket: `feature/user-authentication`
+- Interactive prompt normalizes ticket-id to lowercase before branch creation.
+- Placeholder prompts are generated from `branch-pattern` in declared order.
+- Validation and branch creation use the same template/pattern rules.
 
-### Git Hooks Integration
+## Configuration
 
-#### With Husky
+Configuration is loaded via `cosmiconfig` (for example `package.json`, `.elsikora/git-branch-lint.config.js`, `.elsikora/git-branch-lint.config.ts`).
 
-```bash
-# Install Husky
-npm install --save-dev husky
-
-# Initialize Husky
-npx husky init
+Rule semantics:
 
-# Add pre-push hook
-echo "npx @elsikora/git-branch-lint" > .husky/pre-push
-```
+- `branch-pattern` defines placeholders with `:placeholder` tokens.
+- Placeholder naming supports lowercase letters, digits, and hyphens (for example `:jira-ticket`).
+- `:type` is validated against configured `branches`.
+- `branch-subject-pattern` supports:
+  - `string` - shared regex for all non-`type` placeholders.
+  - `object` - regex per placeholder key (for example `scope`, `description`, `ticket`).
+- Optional placeholders are supported when the token is followed by `-` in `branch-pattern` (for example `:ticket-`).
+- Before branch creation, the final assembled name is validated again with full lint rules.
 
-#### With lint-staged
+### JavaScript Example
 
 ```javascript
-// lint-staged.config.js
 export default {
-  '*': () => 'npx @elsikora/git-branch-lint'
+	branches: {
+		feature: { title: "Feature", description: "New functionality" },
+		bugfix: { title: "Bugfix", description: "Bug fixes" },
+		hotfix: { title: "Hotfix", description: "Urgent fixes" },
+	},
+	ignore: ["dev"],
+	rules: {
+		"branch-pattern": ":type/:ticket-:name",
+		"branch-subject-pattern": "[a-z0-9-]+",
+		"branch-prohibited": ["main", "master", "release"],
+		"branch-min-length": 5,
+		"branch-max-length": 50,
+	},
 };
 ```
 
-### CI/CD Integration
-
-#### GitHub Actions
+### Advanced Placeholder Example
 
-```yaml
-name: Branch Lint
-on: [push, pull_request]
-
-jobs:
-  lint-branch:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-      - run: npm ci
-      - run: npx @elsikora/git-branch-lint
+```javascript
+export default {
+	branches: ["feat", "fix", "chore"],
+	rules: {
+		"branch-pattern": ":scope/:type/:description",
+		"branch-subject-pattern": {
+			scope: "(web|api|shared)",
+			description: "[a-z0-9-]+",
+		},
+	},
+};
 ```
 
-#### GitLab CI
+Valid branch example: `web/feat/shopping-cart`.
 
-```yaml
-branch-lint:
-  stage: test
-  script:
-    - npm ci
-    - npx @elsikora/git-branch-lint
-  only:
-    - branches
-```
+### TypeScript Example
 
-### Advanced Patterns
+```typescript
+import type { IBranchLintConfig } from "@elsikora/git-branch-lint";
 
-#### Jira Integration Pattern
+const config: IBranchLintConfig = {
+	branches: {
+		feature: { title: "Feature", description: "New functionality" },
+		bugfix: { title: "Bugfix", description: "Bug fixes" },
+		hotfix: { title: "Hotfix", description: "Urgent fixes" },
+	},
+	ignore: ["dev"],
+	rules: {
+		"branch-pattern": ":type/:ticket-:name",
+		"branch-subject-pattern": "[a-z0-9-]+",
+		"branch-prohibited": ["main", "master", "release"],
+		"branch-min-length": 5,
+		"branch-max-length": 50,
+	},
+};
 
-```javascript
-{
-  rules: {
-    "branch-pattern": ":type/:ticket-:description",
-    "branch-subject-pattern": {
-      "ticket": "[a-z]{2,}-[0-9]+",
-      "description": "[a-z0-9-]+"
-    }
-  }
-}
-// Valid: feature/proj-123-user-authentication
+export default config;
 ```
 
-#### Monorepo Pattern
+### `package.json` Example
 
-```javascript
+```json
 {
-  rules: {
-    "branch-pattern": ":scope/:type/:name",
-    "branch-subject-pattern": {
-      "scope": "(web|api|shared|docs)",
-      "type": "(feat|fix|chore)",
-      "name": "[a-z0-9-]+"
-    }
-  }
+	"elsikora": {
+		"git-branch-lint": {
+			"branches": ["feature", "bugfix", "hotfix"],
+			"rules": {
+				"branch-pattern": ":type/:ticket-:name",
+				"branch-subject-pattern": "[a-z0-9-]+",
+				"branch-prohibited": ["main", "master", "release"]
+			}
+		}
+	}
 }
-// Valid: web/feat/shopping-cart
 ```
 
-## 🛣 Roadmap
-| Task / Feature | Status |
-|----------------|--------|
-| Core branch validation engine | ✅ Done |
-| Interactive branch creation wizard | ✅ Done |
-| Multiple configuration format support | ✅ Done |
-| TypeScript support | ✅ Done |
-| Comprehensive test coverage | ✅ Done |
-| VS Code extension | 🚧 In Progress |
-| Branch name auto-suggestions | 🚧 In Progress |
-| Custom validation rules plugin system | 🚧 In Progress |
-| Branch naming statistics dashboard | 🚧 In Progress |
-| Integration with popular Git GUIs | 🚧 In Progress |
-| AI-powered branch name generator | 🚧 In Progress |
-
-## ❓ FAQ
-## ❓ Frequently Asked Questions
-
-### **Q: Can I use this with existing branches?**
-A: Yes! The `ignore` configuration option allows you to exclude existing branches from validation. This is perfect for grandfathering in old branches while enforcing rules on new ones.
-
-### **Q: How do I handle different patterns for different teams?**
-A: You can create team-specific configuration files and use environment variables or Git config to load the appropriate one:
-```bash
-GIT_BRANCH_LINT_CONFIG=.team-frontend.config.js npx @elsikora/git-branch-lint
-```
+## Clean Architecture Rules
 
-### **Q: Can I validate branch names in my IDE?**
-A: While we're working on official IDE extensions, you can configure your IDE to run the validation as an external tool or use it with pre-commit hooks.
+Repository standards enforced in this codebase:
 
-### **Q: What happens if I try to push an invalid branch?**
-A: When integrated with Git hooks, the push will be prevented and you'll see a helpful error message explaining what's wrong and how to fix it.
+- Business rules live in `domain` and are consumed via `application` use cases.
+- `presentation` does I/O only; it must not own business validation rules.
+- `infrastructure` contains adapters only; default domain rules are defined outside adapter implementation.
+- `application` depends on domain contracts, not concrete infrastructure classes.
+- Types/interfaces are extracted into dedicated type/interface files for reusable contracts.
+- Import order and class member ordering are lint-enforced and must remain consistent.
 
-### **Q: Can I use custom regex patterns?**
-A: Absolutely! The `branch-subject-pattern` rule accepts any valid JavaScript regex pattern, giving you complete control over validation.
+## Development
 
-### **Q: Is this compatible with Git Flow or GitHub Flow?**
-A: Yes! The default configuration works well with both workflows, and you can easily customize it to match your specific flow requirements.
+Common scripts:
 
-### **Q: How do I migrate from other branch linting tools?**
-A: Git-Branch-Lint's configuration is designed to be intuitive. Most configurations from other tools can be adapted by mapping their patterns to our rule system.
+```bash
+npm run lint
+npm run lint:types
+npm run test:unit
+npm run test:e2e
+```
 
-## 🔒 License
-This project is licensed under **MIT License - see the [LICENSE](LICENSE) file for details.
+## License
 
-Maintained with ❤️ by [ElsiKora](https://github.com/ElsiKora)**.
+MIT. See [`LICENSE`](LICENSE).

package/bin/application/type/branch-placeholder-definition.type.d.ts

@@ -0,0 +1,7 @@
+export interface IBranchPlaceholderDefinition {
+    example?: string;
+    isOptional: boolean;
+    isTypePlaceholder: boolean;
+    patternSource?: string;
+    placeholderName: string;
+}

package/bin/application/type/build-branch-name-parameters.type.d.ts

@@ -0,0 +1,4 @@
+export interface IBuildBranchNameParameters {
+    branchPattern: string;
+    placeholderValues: Record<string, string>;
+}

package/bin/application/type/get-branch-placeholder-definitions-parameters.type.d.ts

@@ -0,0 +1,4 @@
+import type { IBranchLintConfig } from "../../domain/type/config.type";
+export interface IGetBranchPlaceholderDefinitionsParameters {
+    config: IBranchLintConfig;
+}

package/bin/application/type/validate-branch-placeholder-value-parameters.type.d.ts

@@ -0,0 +1,6 @@
+export interface IValidateBranchPlaceholderValueParameters {
+    isOptional: boolean;
+    patternSource: string;
+    placeholderName: string;
+    value: string;
+}

package/bin/application/use-cases/build-branch-name.use-case.d.ts

@@ -0,0 +1,10 @@
+import type { IBuildBranchNameParameters } from "../type/build-branch-name-parameters.type";
+import { BranchTemplatePolicy } from "../../domain/policy/branch-template.policy";
+/**
+ * Use case for assembling a branch name from validated user inputs.
+ */
+export declare class BuildBranchNameUseCase {
+    private readonly branchTemplatePolicy;
+    constructor(branchTemplatePolicy?: BranchTemplatePolicy);
+    execute(parameters: IBuildBranchNameParameters): string;
+}

package/bin/application/use-cases/get-branch-pattern.use-case.d.ts

@@ -0,0 +1,8 @@
+import type { IBranchLintConfig } from "../../domain/type/config.type";
+/**
+ * Use case for retrieving effective branch pattern.
+ */
+export declare class GetBranchPatternUseCase {
+    private readonly DEFAULT_BRANCH_PATTERN;
+    execute(config: IBranchLintConfig): string;
+}

package/bin/application/use-cases/get-branch-placeholder-definitions.use-case.d.ts

@@ -0,0 +1,11 @@
+import type { IBranchPlaceholderDefinition } from "../type/branch-placeholder-definition.type";
+import type { IGetBranchPlaceholderDefinitionsParameters } from "../type/get-branch-placeholder-definitions-parameters.type";
+import { BranchTemplatePolicy } from "../../domain/policy/branch-template.policy";
+/**
+ * Use case for resolving placeholder definitions from branch pattern config.
+ */
+export declare class GetBranchPlaceholderDefinitionsUseCase {
+    private readonly branchTemplatePolicy;
+    constructor(branchTemplatePolicy?: BranchTemplatePolicy);
+    execute(parameters: IGetBranchPlaceholderDefinitionsParameters): Array<IBranchPlaceholderDefinition>;
+}

package/bin/application/use-cases/get-current-branch.use-case.d.ts

@@ -3,11 +3,7 @@ import type { IBranchRepository } from "../../domain/interface/branch.repository
  * Use case for getting the current branch name
  */
 export declare class GetCurrentBranchUseCase {
-    private readonly BRANCH_REPOSITORY;
-    /**
-     * Constructor
-     * @param branchRepository The branch repository
-     */
+    private readonly branchRepository;
     constructor(branchRepository: IBranchRepository);
     /**
      * Execute the use case

package/bin/application/use-cases/lint-branch-name.use-case.d.ts

@@ -1,8 +1,11 @@
 import type { IBranchLintConfig } from "../../domain/type/config.type";
+import { BranchTemplatePolicy } from "../../domain/policy/branch-template.policy";
 /**
  * Use case for linting branch names
  */
 export declare class LintBranchNameUseCase {
+    private readonly BRANCH_TEMPLATE_POLICY;
+    constructor(branchTemplatePolicy?: BranchTemplatePolicy);
     /**
      * Execute the use case
      * @param branchName The branch name to lint
@@ -13,15 +16,6 @@ export declare class LintBranchNameUseCase {
      * @throws {BranchTooLongError} When branch name is longer than the maximum length
      */
     execute(branchName: string, config: IBranchLintConfig): void;
-    /**
-     * Test a branch name against a specific pattern
-     * @param branchName The branch name to test
-     * @param pattern The pattern to test against
-     * @param branchTypes Available branch types
-     * @param subjectNamePattern Pattern for the name/description part
-     * @returns true if pattern matches
-     */
-    private testPattern;
     /**
      * Validate the branch name against the pattern
      * @param branchName The branch name to validate

package/bin/application/use-cases/normalize-ticket-id.use-case.d.ts

@@ -0,0 +1,9 @@
+import { TicketIdPolicy } from "../../domain/policy/ticket-id.policy";
+/**
+ * Use case for normalizing optional ticket identifier input.
+ */
+export declare class NormalizeTicketIdUseCase {
+    private readonly ticketIdPolicy;
+    constructor(ticketIdPolicy?: TicketIdPolicy);
+    execute(ticketId: string): string;
+}

package/bin/application/use-cases/validate-branch-placeholder-value.use-case.d.ts

@@ -0,0 +1,8 @@
+import type { IInputValidationResult } from "../../domain/type/input-validation-result.type";
+import type { IValidateBranchPlaceholderValueParameters } from "../type/validate-branch-placeholder-value-parameters.type";
+/**
+ * Use case for validating interactive placeholder values.
+ */
+export declare class ValidateBranchPlaceholderValueUseCase {
+    execute(parameters: IValidateBranchPlaceholderValueParameters): IInputValidationResult;
+}

package/bin/domain/config/default-branch-lint-config.d.ts

@@ -0,0 +1,2 @@
+import type { IBranchLintConfig } from "../type/config.type";
+export declare const DEFAULT_BRANCH_LINT_CONFIG: IBranchLintConfig;

package/bin/domain/constant/branch-pattern.constant.d.ts

@@ -0,0 +1 @@
+export declare const DEFAULT_BRANCH_SUBJECT_PATTERN_SOURCE: string;

package/bin/domain/constant/ticket-id.constant.d.ts

@@ -0,0 +1,3 @@
+export declare const TICKET_ID_ERROR_MESSAGE: string;
+export declare const TICKET_ID_EXAMPLE: string;
+export declare const TICKET_ID_PATTERN_SOURCE: string;

package/bin/domain/errors/lint.error.d.ts

@@ -16,6 +16,12 @@ export declare class BranchTooLongError extends LintError {
 export declare class BranchTooShortError extends LintError {
     constructor(branchName: string, minLength: number);
 }
+/**
+ * Error thrown when a branch placeholder pattern in config is invalid.
+ */
+export declare class InvalidBranchPatternConfigError extends LintError {
+    constructor(placeholderName: string, patternSource: string);
+}
 /**
  * Error thrown when branch name doesn't match the pattern
  */

package/bin/domain/policy/branch-template.policy.d.ts

@@ -0,0 +1,18 @@
+import type { TBranchSubjectPattern } from "../type/branch-subject-pattern.type";
+/**
+ * Domain policy for working with branch templates and placeholders.
+ */
+export declare class BranchTemplatePolicy {
+    private static readonly PLACEHOLDER_PATTERN;
+    buildBranchName(branchPattern: string, placeholderValues: Record<string, string>): string;
+    buildValidationPatterns(branchPattern: string): Array<string>;
+    getPlaceholders(branchPattern: string): Array<string>;
+    isPlaceholderOptional(branchPattern: string, placeholderName: string): boolean;
+    resolvePlaceholderPatternSource(placeholderName: string, branchTypes: Array<string>, subjectPattern?: TBranchSubjectPattern): string;
+    private createAlternationPattern;
+    private escapeRegex;
+    private isDelimiter;
+    private normalizeBranchNameDelimiters;
+    private removeOptionalPlaceholder;
+    private trimDelimiterEdges;
+}

package/bin/domain/policy/ticket-id.policy.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Domain policy for ticket identifier normalization and validation.
+ */
+export declare class TicketIdPolicy {
+    private static readonly TICKET_ID_PATTERN;
+    isEmpty(candidate: string): boolean;
+    isValid(candidate: string): boolean;
+    normalize(candidate: string): string;
+}

package/bin/domain/type/branch-subject-pattern.type.d.ts

@@ -0,0 +1 @@
+export type TBranchSubjectPattern = Record<string, string> | string;