codd-dev 1.2.0__tar.gz → 1.3.0__tar.gz

{codd_dev-1.2.0 → codd_dev-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codd-dev
-Version: 1.2.0
+Version: 1.3.0
 Summary: CoDD: Coherence-Driven Development — cross-artifact change impact analysis
 Project-URL: Homepage, https://github.com/yohey-w/codd-dev
 Project-URL: Repository, https://github.com/yohey-w/codd-dev
@@ -59,7 +59,7 @@ Description-Content-Type: text/markdown
 pip install codd-dev
 ```
 
-**Public Alpha** — `init` / `scan` / `impact` are stable; `validate` is alpha.
+**v1.2.0** — `init` / `scan` / `impact` are stable. `generate` / `implement` / `assemble` / `validate` / `extract` are alpha.
 
 ---
 
@@ -109,6 +109,8 @@ CoDD is **harness-agnostic** — works with Claude Code, Copilot, Cursor, or any
 
 ## Quick Start
 
+### Greenfield (new project)
+
 ```bash
 pip install codd-dev
 mkdir my-project && cd my-project && git init
@@ -117,79 +119,142 @@ mkdir my-project && cd my-project && git init
 codd init --project-name "my-project" --language "typescript" \
   --requirements spec.txt
 
-# AI generates design docs (wave_config auto-generated)
-codd generate --wave 2
+# AI designs the document dependency graph
+codd plan --init
 
-# Build dependency graph → analyze impact
-codd scan
-codd impact
+# Generate design docs wave by wave
+waves=$(codd plan --waves)
+for wave in $(seq 1 $waves); do
+  codd generate --wave $wave
+done
+
+# Quality gate — catch AI laziness (TODOs, placeholders)
+codd validate
+
+# Generate code from design docs
+sprints=$(codd plan --sprints)
+for sprint in $(seq 1 $sprints); do
+  codd implement --sprint $sprint
+done
+
+# Assemble code fragments into a buildable project
+codd assemble
 ```
 
-## 5-Minute Demo — See CoDD in Action
+### Brownfield (existing project)
 
-We'll build **TaskFlow**, a task management app. Write **requirements in plain text**, let CoDD + AI handle everything else.
+```bash
+codd extract              # Reverse-engineer design docs from code
+codd plan --init          # Generate wave_config from extracted docs
+codd scan                 # Build dependency graph
+codd impact               # Change impact analysis
+```
+
+## 5-Minute Greenfield Demo — Spec to Working App
 
-### Step 1: Write your requirements (any format — txt, md, doc)
+37 lines of spec → 6 design docs (1,353 lines) → 102 code files (6,445 lines) → TypeScript strict build passes.
+
+### Step 1: Write your requirements
 
 ```text
-# TaskFlow — Requirements
+# TaskFlow — Personal Todo App
 
 ## Functional Requirements
-- User auth (email + Google OAuth)
-- Workspace management (teams, roles, invites)
-- Task CRUD with assignees, labels, due dates
-- Real-time updates (WebSocket)
-- File attachments (S3)
-- Notification system (in-app + email)
+- Task CRUD: create, read, update, delete tasks
+- Each task has: title, description (optional), due date (optional),
+  priority (low/medium/high), completed status
+- Task list with filtering by: status (all/active/completed), priority
+- Local state management (no backend, localStorage)
+
+## UI Requirements
+- Single-page app with responsive layout (mobile-first)
+- Dark theme with accent color (#3b82f6)
+- Floating action button opens a modal form
+- Toast notifications on create/update/delete
+- Keyboard shortcuts: Enter to submit, Escape to close modal
 
 ## Constraints
-- Next.js + Prisma + PostgreSQL
-- Row-level security for workspace isolation
-- All API endpoints rate-limited
+- Next.js 15 App Router with React Server Components
+- Tailwind CSS
+- TypeScript strict mode
+- Deploy-ready as static export
 ```
 
-Save this as `spec.txt`. That's it — no special formatting needed.
-
-### Step 2: Initialize CoDD
+### Step 2: Run the pipeline
 
 ```bash
 pip install codd-dev
-mkdir taskflow && cd taskflow && git init
-codd init --project-name "taskflow" --language "typescript" \
-  --requirements spec.txt
+codd init --requirements spec.md
+codd plan --init                          # AI designs the wave structure
+
+waves=$(codd plan --waves)                # → 4
+for wave in $(seq 1 $waves); do
+  codd generate --wave $wave              # design docs, wave by wave
+done
+
+codd validate                             # quality gate
+
+sprints=$(codd plan --sprints)            # → 17
+for sprint in $(seq 1 $sprints); do
+  codd implement --sprint $sprint         # code from design docs
+done
+
+codd assemble                             # integrate into buildable project
+npm run build                             # TypeScript strict, zero errors
 ```
 
-CoDD adds frontmatter (`node_id`, `type`, dependency metadata) automatically. You never touch it.
+No interactive AI chat at any step. Every AI call goes through `claude --print` — prompt in, text out. **Harness as Code**: the entire workflow is a shell script.
 
-### Step 3: AI generates design docs
+### Step 3: Model role separation
 
 ```bash
-codd generate --wave 2   # System design + API design
-codd generate --wave 3   # DB design + Auth design
-codd generate --wave 4   # Test strategy
+# Design docs — needs judgment, use Opus
+codd generate --wave 1 --ai-cmd 'claude --print --model claude-opus-4-6 --tools ""'
+
+# Code generation — needs volume, use Codex (or Sonnet)
+codd implement --sprint 1 --ai-cmd 'codex --full-auto -q'
 ```
 
-`wave_config` is auto-generated from your requirements. Each design doc gets frontmatter, `depends_on` declarations, and a `modules` field linking it to source code modules — all derived, nothing manual.
+## 5-Minute Brownfield Demo — Change Impact Analysis
+
+Already have a codebase? CoDD tracks what's affected when requirements change.
 
-### Step 4: Build the dependency graph
+### Step 1: Write requirements and generate design docs
+
+```text
+# TaskFlow — Requirements
+
+## Functional Requirements
+- User auth (email + Google OAuth)
+- Workspace management (teams, roles, invites)
+- Task CRUD with assignees, labels, due dates
+- Real-time updates (WebSocket)
+- File attachments (S3)
+- Notification system (in-app + email)
+
+## Constraints
+- Next.js + Prisma + PostgreSQL
+- Row-level security for workspace isolation
+- All API endpoints rate-limited
+```
 
 ```bash
+codd init --requirements spec.txt
+codd plan --init
+waves=$(codd plan --waves)
+for wave in $(seq 1 $waves); do codd generate --wave $wave; done
 codd scan
 ```
 
 ```
-Frontmatter: 7 documents in docs
 Scan complete:
   Documents with frontmatter: 7
   Graph: 7 nodes, 15 edges
-  Evidence: 15 total (0 human, 15 auto)
 ```
 
-7 docs, 15 dependency edges. Zero config written by hand.
+### Step 2: Change requirements mid-project
 
-### Step 5: Change requirements mid-project
-
-Your PM asks for SSO and audit logging. Open `docs/requirements/requirements.md` and add:
+Your PM asks for SSO and audit logging. Add to `docs/requirements/requirements.md`:
 
 ```text
 ## Additional Requirements (v1.1)
@@ -197,16 +262,11 @@ Your PM asks for SSO and audit logging. Open `docs/requirements/requirements.md`
 - Audit logging (record & export all operations)
 ```
 
-Save the file and ask CoDD what's affected:
-
 ```bash
 codd impact    # detects uncommitted changes automatically
 ```
 
 ```
-Changed files: 1
-  - docs/requirements/requirements.md → req:taskflow-requirements
-
 # CoDD Impact Report
 
 ## Green Band (high confidence, auto-propagate)
@@ -221,14 +281,9 @@ Changed files: 1
 | Target                  | Depth | Confidence |
 |-------------------------|-------|------------|
 | test:test-strategy      | 2     | 0.90       |
-
-## Gray Band (informational)
-| Target                  | Depth | Confidence |
-|-------------------------|-------|------------|
-| plan:implementation     | 2     | 0.00       |
 ```
 
-**2 lines changed → 6 out of 7 docs affected.** Green band: AI auto-updates. Amber: human reviews. Gray: informational. You know exactly what to fix before anything breaks.
+**2 lines changed → 6 out of 7 docs affected.** Green band: AI auto-updates. Amber: human reviews. You know exactly what to fix before anything breaks.
 
 ## Wave-Based Generation
 
@@ -296,6 +351,22 @@ ai_commands:
 
 **Resolution priority**: CLI `--ai-cmd` flag > `ai_commands.{command}` > `ai_command` > built-in default (Opus).
 
+### Claude Code Context Interference
+
+When `claude --print` runs inside a project directory, it auto-discovers `CLAUDE.md` and loads project-level system prompts. These instructions can conflict with CoDD's generation prompts, causing format validation failures like:
+
+```
+Error: AI command returned unstructured summary for 'ADR: ...'; missing section headings
+```
+
+**Fix**: Use `--system-prompt` to override project context with a focused instruction:
+
+```yaml
+ai_command: "claude --print --model claude-opus-4-6 --system-prompt 'You are a technical document generator. Output only the requested Markdown document. Follow section heading instructions exactly.'"
+```
+
+> **Note**: `--bare` strips all context but also disables OAuth authentication. Use `--system-prompt` instead — it overrides `CLAUDE.md` while preserving auth.
+
 ## Config Directory Discovery
 
 By default, `codd init` creates a `codd/` directory. If your project already has a `codd/` directory (e.g., it's your source code package), use `--config-dir`:
@@ -569,8 +640,10 @@ If CoDD can't manage itself, it shouldn't manage your project.
 
 ## Articles
 
-- [Zenn (Japanese): CoDD deep-dive](https://zenn.dev/shio_shoppaize/articles/shogun-codd-coherence)
+- [dev.to (English): Harness as Code — Treating AI Workflows Like Infrastructure](https://dev.to/yohey-w/harness-as-code-treating-ai-workflows-like-infrastructure-27ni)
 - [dev.to (English): What Happens After "Spec First"](https://dev.to/yohey-w/codd-coherence-driven-development-what-happens-after-spec-first-514f)
+- [Zenn (Japanese): Harness as Code — CoDD活用ガイド #1 spec → 設計書 → コード](https://zenn.dev/shio_shoppaize/articles/codd-greenfield-guide)
+- [Zenn (Japanese): CoDD deep-dive](https://zenn.dev/shio_shoppaize/articles/shogun-codd-coherence)
 
 ## License
 

{codd_dev-1.2.0 → codd_dev-1.3.0}/README.md

@@ -22,7 +22,7 @@
 pip install codd-dev
 ```
 
-**Public Alpha** — `init` / `scan` / `impact` are stable; `validate` is alpha.
+**v1.2.0** — `init` / `scan` / `impact` are stable. `generate` / `implement` / `assemble` / `validate` / `extract` are alpha.
 
 ---
 
@@ -72,6 +72,8 @@ CoDD is **harness-agnostic** — works with Claude Code, Copilot, Cursor, or any
 
 ## Quick Start
 
+### Greenfield (new project)
+
 ```bash
 pip install codd-dev
 mkdir my-project && cd my-project && git init
@@ -80,79 +82,142 @@ mkdir my-project && cd my-project && git init
 codd init --project-name "my-project" --language "typescript" \
   --requirements spec.txt
 
-# AI generates design docs (wave_config auto-generated)
-codd generate --wave 2
+# AI designs the document dependency graph
+codd plan --init
 
-# Build dependency graph → analyze impact
-codd scan
-codd impact
+# Generate design docs wave by wave
+waves=$(codd plan --waves)
+for wave in $(seq 1 $waves); do
+  codd generate --wave $wave
+done
+
+# Quality gate — catch AI laziness (TODOs, placeholders)
+codd validate
+
+# Generate code from design docs
+sprints=$(codd plan --sprints)
+for sprint in $(seq 1 $sprints); do
+  codd implement --sprint $sprint
+done
+
+# Assemble code fragments into a buildable project
+codd assemble
 ```
 
-## 5-Minute Demo — See CoDD in Action
+### Brownfield (existing project)
 
-We'll build **TaskFlow**, a task management app. Write **requirements in plain text**, let CoDD + AI handle everything else.
+```bash
+codd extract              # Reverse-engineer design docs from code
+codd plan --init          # Generate wave_config from extracted docs
+codd scan                 # Build dependency graph
+codd impact               # Change impact analysis
+```
+
+## 5-Minute Greenfield Demo — Spec to Working App
 
-### Step 1: Write your requirements (any format — txt, md, doc)
+37 lines of spec → 6 design docs (1,353 lines) → 102 code files (6,445 lines) → TypeScript strict build passes.
+
+### Step 1: Write your requirements
 
 ```text
-# TaskFlow — Requirements
+# TaskFlow — Personal Todo App
 
 ## Functional Requirements
-- User auth (email + Google OAuth)
-- Workspace management (teams, roles, invites)
-- Task CRUD with assignees, labels, due dates
-- Real-time updates (WebSocket)
-- File attachments (S3)
-- Notification system (in-app + email)
+- Task CRUD: create, read, update, delete tasks
+- Each task has: title, description (optional), due date (optional),
+  priority (low/medium/high), completed status
+- Task list with filtering by: status (all/active/completed), priority
+- Local state management (no backend, localStorage)
+
+## UI Requirements
+- Single-page app with responsive layout (mobile-first)
+- Dark theme with accent color (#3b82f6)
+- Floating action button opens a modal form
+- Toast notifications on create/update/delete
+- Keyboard shortcuts: Enter to submit, Escape to close modal
 
 ## Constraints
-- Next.js + Prisma + PostgreSQL
-- Row-level security for workspace isolation
-- All API endpoints rate-limited
+- Next.js 15 App Router with React Server Components
+- Tailwind CSS
+- TypeScript strict mode
+- Deploy-ready as static export
 ```
 
-Save this as `spec.txt`. That's it — no special formatting needed.
-
-### Step 2: Initialize CoDD
+### Step 2: Run the pipeline
 
 ```bash
 pip install codd-dev
-mkdir taskflow && cd taskflow && git init
-codd init --project-name "taskflow" --language "typescript" \
-  --requirements spec.txt
+codd init --requirements spec.md
+codd plan --init                          # AI designs the wave structure
+
+waves=$(codd plan --waves)                # → 4
+for wave in $(seq 1 $waves); do
+  codd generate --wave $wave              # design docs, wave by wave
+done
+
+codd validate                             # quality gate
+
+sprints=$(codd plan --sprints)            # → 17
+for sprint in $(seq 1 $sprints); do
+  codd implement --sprint $sprint         # code from design docs
+done
+
+codd assemble                             # integrate into buildable project
+npm run build                             # TypeScript strict, zero errors
 ```
 
-CoDD adds frontmatter (`node_id`, `type`, dependency metadata) automatically. You never touch it.
+No interactive AI chat at any step. Every AI call goes through `claude --print` — prompt in, text out. **Harness as Code**: the entire workflow is a shell script.
 
-### Step 3: AI generates design docs
+### Step 3: Model role separation
 
 ```bash
-codd generate --wave 2   # System design + API design
-codd generate --wave 3   # DB design + Auth design
-codd generate --wave 4   # Test strategy
+# Design docs — needs judgment, use Opus
+codd generate --wave 1 --ai-cmd 'claude --print --model claude-opus-4-6 --tools ""'
+
+# Code generation — needs volume, use Codex (or Sonnet)
+codd implement --sprint 1 --ai-cmd 'codex --full-auto -q'
 ```
 
-`wave_config` is auto-generated from your requirements. Each design doc gets frontmatter, `depends_on` declarations, and a `modules` field linking it to source code modules — all derived, nothing manual.
+## 5-Minute Brownfield Demo — Change Impact Analysis
+
+Already have a codebase? CoDD tracks what's affected when requirements change.
 
-### Step 4: Build the dependency graph
+### Step 1: Write requirements and generate design docs
+
+```text
+# TaskFlow — Requirements
+
+## Functional Requirements
+- User auth (email + Google OAuth)
+- Workspace management (teams, roles, invites)
+- Task CRUD with assignees, labels, due dates
+- Real-time updates (WebSocket)
+- File attachments (S3)
+- Notification system (in-app + email)
+
+## Constraints
+- Next.js + Prisma + PostgreSQL
+- Row-level security for workspace isolation
+- All API endpoints rate-limited
+```
 
 ```bash
+codd init --requirements spec.txt
+codd plan --init
+waves=$(codd plan --waves)
+for wave in $(seq 1 $waves); do codd generate --wave $wave; done
 codd scan
 ```
 
 ```
-Frontmatter: 7 documents in docs
 Scan complete:
   Documents with frontmatter: 7
   Graph: 7 nodes, 15 edges
-  Evidence: 15 total (0 human, 15 auto)
 ```
 
-7 docs, 15 dependency edges. Zero config written by hand.
+### Step 2: Change requirements mid-project
 
-### Step 5: Change requirements mid-project
-
-Your PM asks for SSO and audit logging. Open `docs/requirements/requirements.md` and add:
+Your PM asks for SSO and audit logging. Add to `docs/requirements/requirements.md`:
 
 ```text
 ## Additional Requirements (v1.1)
@@ -160,16 +225,11 @@ Your PM asks for SSO and audit logging. Open `docs/requirements/requirements.md`
 - Audit logging (record & export all operations)
 ```
 
-Save the file and ask CoDD what's affected:
-
 ```bash
 codd impact    # detects uncommitted changes automatically
 ```
 
 ```
-Changed files: 1
-  - docs/requirements/requirements.md → req:taskflow-requirements
-
 # CoDD Impact Report
 
 ## Green Band (high confidence, auto-propagate)
@@ -184,14 +244,9 @@ Changed files: 1
 | Target                  | Depth | Confidence |
 |-------------------------|-------|------------|
 | test:test-strategy      | 2     | 0.90       |
-
-## Gray Band (informational)
-| Target                  | Depth | Confidence |
-|-------------------------|-------|------------|
-| plan:implementation     | 2     | 0.00       |
 ```
 
-**2 lines changed → 6 out of 7 docs affected.** Green band: AI auto-updates. Amber: human reviews. Gray: informational. You know exactly what to fix before anything breaks.
+**2 lines changed → 6 out of 7 docs affected.** Green band: AI auto-updates. Amber: human reviews. You know exactly what to fix before anything breaks.
 
 ## Wave-Based Generation
 
@@ -259,6 +314,22 @@ ai_commands:
 
 **Resolution priority**: CLI `--ai-cmd` flag > `ai_commands.{command}` > `ai_command` > built-in default (Opus).
 
+### Claude Code Context Interference
+
+When `claude --print` runs inside a project directory, it auto-discovers `CLAUDE.md` and loads project-level system prompts. These instructions can conflict with CoDD's generation prompts, causing format validation failures like:
+
+```
+Error: AI command returned unstructured summary for 'ADR: ...'; missing section headings
+```
+
+**Fix**: Use `--system-prompt` to override project context with a focused instruction:
+
+```yaml
+ai_command: "claude --print --model claude-opus-4-6 --system-prompt 'You are a technical document generator. Output only the requested Markdown document. Follow section heading instructions exactly.'"
+```
+
+> **Note**: `--bare` strips all context but also disables OAuth authentication. Use `--system-prompt` instead — it overrides `CLAUDE.md` while preserving auth.
+
 ## Config Directory Discovery
 
 By default, `codd init` creates a `codd/` directory. If your project already has a `codd/` directory (e.g., it's your source code package), use `--config-dir`:
@@ -532,8 +603,10 @@ If CoDD can't manage itself, it shouldn't manage your project.
 
 ## Articles
 
-- [Zenn (Japanese): CoDD deep-dive](https://zenn.dev/shio_shoppaize/articles/shogun-codd-coherence)
+- [dev.to (English): Harness as Code — Treating AI Workflows Like Infrastructure](https://dev.to/yohey-w/harness-as-code-treating-ai-workflows-like-infrastructure-27ni)
 - [dev.to (English): What Happens After "Spec First"](https://dev.to/yohey-w/codd-coherence-driven-development-what-happens-after-spec-first-514f)
+- [Zenn (Japanese): Harness as Code — CoDD活用ガイド #1 spec → 設計書 → コード](https://zenn.dev/shio_shoppaize/articles/codd-greenfield-guide)
+- [Zenn (Japanese): CoDD deep-dive](https://zenn.dev/shio_shoppaize/articles/shogun-codd-coherence)
 
 ## License
 

{codd_dev-1.2.0 → codd_dev-1.3.0}/codd/__init__.py

@@ -1,3 +1,3 @@
 """CoDD — Coherence-Driven Development."""
 
-__version__ = "0.4.0"
+__version__ = "1.3.0"

{codd_dev-1.2.0 → codd_dev-1.3.0}/codd/cli.py

@@ -1,4 +1,4 @@
-"""CoDD CLI — codd init / scan / impact / plan."""
+"""CoDD CLI — codd init / scan / impact / require / plan."""
 
 import click
 import json
@@ -175,8 +175,8 @@ def generate(wave: int, path: str, force: bool, ai_cmd: str | None, feedback: st
     help="Override AI CLI command (defaults to codd.yaml ai_command or 'claude --print')",
 )
 @click.option("--feedback", default=None, help="Review feedback to address in this restoration (from codd review)")
-def restore(wave: int, path: str, force: bool, ai_cmd: str | None, feedback: str | None):
-    """Restore design documents from extracted codebase facts (brownfield).
+def restore(wave: int, path: str, force: bool, ai_cmd: str | None, feedback: str | None):
+    """Restore design documents from extracted codebase facts (brownfield).
 
     Unlike 'generate' which creates design docs from requirements (greenfield),
     'restore' reconstructs design documents from extracted code analysis.
@@ -206,15 +206,68 @@ def restore(wave: int, path: str, force: bool, ai_cmd: str | None, feedback: str
             restored += 1
         else:
             skipped += 1
-
-    click.echo(f"Wave {wave}: {restored} restored, {skipped} skipped")
-
-
-@main.command()
-@click.option("--diff", default="HEAD", help="Git diff target (default: HEAD, shows uncommitted changes)")
-@click.option("--path", default=".", help="Project root directory")
-@click.option("--update", is_flag=True, help="Actually update affected design docs via AI")
-@click.option(
+
+    click.echo(f"Wave {wave}: {restored} restored, {skipped} skipped")
+
+
+@main.command()
+@click.option("--path", default=".", help="Project root directory")
+@click.option("--output", default="docs/requirements/", help="Output directory for generated requirements")
+@click.option("--scope", default=None, help="Limit to a specific service boundary")
+@click.option(
+    "--ai-cmd",
+    default=None,
+    help="Override AI CLI command (defaults to codd.yaml ai_command or merged CoDD defaults)",
+)
+@click.option("--force", is_flag=True, help="Overwrite existing files")
+@click.option("--feedback", default=None, help="Review feedback from previous generation")
+def require(path: str, output: str, scope: str | None, ai_cmd: str | None, force: bool, feedback: str | None):
+    """Infer requirements from extracted codebase facts (brownfield).
+
+    Unlike 'restore' which reconstructs design docs from extracted facts,
+    'require' reverse-engineers requirements documents from the same
+    extracted code analysis. Run 'codd extract' first.
+    """
+    from codd.require import run_require
+
+    project_root = Path(path).resolve()
+    _require_codd_dir(project_root)
+
+    try:
+        results = run_require(
+            project_root,
+            output_dir=output,
+            scope=scope,
+            ai_command=ai_cmd,
+            force=force,
+            feedback=feedback,
+        )
+    except (FileNotFoundError, ValueError) as exc:
+        click.echo(f"Error: {exc}")
+        raise SystemExit(1)
+
+    generated = 0
+    skipped = 0
+
+    for result in results:
+        try:
+            rel_path = result.path.relative_to(project_root).as_posix()
+        except ValueError:
+            rel_path = result.path.as_posix()
+        click.echo(f"{result.status.capitalize()}: {rel_path} ({result.node_id})")
+        if result.status == "generated":
+            generated += 1
+        else:
+            skipped += 1
+
+    click.echo(f"Requirements: {generated} generated, {skipped} skipped")
+
+
+@main.command()
+@click.option("--diff", default="HEAD", help="Git diff target (default: HEAD, shows uncommitted changes)")
+@click.option("--path", default=".", help="Project root directory")
+@click.option("--update", is_flag=True, help="Actually update affected design docs via AI")
+@click.option(
     "--ai-cmd",
     default=None,
     help="Override AI CLI command (defaults to codd.yaml ai_command)",

codd_dev-1.2.0/codd/hooks.py → codd_dev-1.3.0/codd/hooks/__init__.py

@@ -12,7 +12,7 @@ from codd.scanner import _extract_frontmatter
 from codd.validator import run_validate
 
 
-HOOK_SOURCE = Path(__file__).parent.parent / "hooks" / "pre-commit"
+HOOK_SOURCE = Path(__file__).parent / "pre-commit"
 
 
 def install_pre_commit_hook(project_root: Path) -> tuple[Path, bool]: