| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Edit Strategy
- + Project Rules
Commands
neither file has anySection tags
0 shared · 1 only in A · 2 only in B- − code-style
- + git-pr
- + do-not
Line diff
yxyxy/HordeForge · .clinerules/97_edit_strategy.md
@@ −1 @@
1# Edit Strategy
2
3When fixing errors:
4
51. Prefer modifying the smallest possible code section.
62. Avoid rewriting entire files.
73. Never repeat the same edit pattern.
8
9If the same fix was already attempted:
10
11The AI must change strategy instead of repeating the edit.
yxyxy/HordeForge · .clinerules/00_project.md
@@ +1 @@
1# Project Rules
2
3Project: HordeForge
4
5HordeForge is an autonomous AI software development orchestrator.
6
7The system reads GitHub issues and automatically performs the full
8software development lifecycle:
9
10Issue
11→ DoD
12→ Specification
13→ BDD scenarios
14→ Test generation (TDD)
15→ Code generation
16→ Test execution
17→ Fix loop
18→ Pull Request
19→ Review
20→ Merge
21→ Issue closing
22
23Core philosophy:
24
251. AI pipeline first
262. Infrastructure second
273. Tests before code
284. Deterministic pipelines
295. Small composable agents
306. Full observability of agent decisions
31
32The primary goal is to build a fully autonomous development pipeline.
33
34Avoid building unnecessary infrastructure before agent functionality exists.
@@ −1 +1 @@
1−# Edit Strategy
1+# Project Rules
22
3−When fixing errors:
3+Project: HordeForge
44
5−1. Prefer modifying the smallest possible code section.
6−2. Avoid rewriting entire files.
7−3. Never repeat the same edit pattern.
5+HordeForge is an autonomous AI software development orchestrator.
86
9−If the same fix was already attempted:
7+The system reads GitHub issues and automatically performs the full
8+software development lifecycle:
109
11−The AI must change strategy instead of repeating the edit.
10+Issue
11+→ DoD
12+→ Specification
13+→ BDD scenarios
14+→ Test generation (TDD)
15+→ Code generation
16+→ Test execution
17+→ Fix loop
18+→ Pull Request
19+→ Review
20+→ Merge
21+→ Issue closing
22+
23+Core philosophy:
24+
25+1. AI pipeline first
26+2. Infrastructure second
27+3. Tests before code
28+4. Deterministic pipelines
29+5. Small composable agents
30+6. Full observability of agent decisions
31+
32+The primary goal is to build a fully autonomous development pipeline.
33+
34+Avoid building unnecessary infrastructure before agent functionality exists.
