bd9790caa1
feat: repeatable mechanical method for patterns mode
...
5 steps: Quantify → Extract one → Decision tree → Cross-refs → Hyperlinks.
Delegation strategy (per-entry, not per-file).
Discovery greps for Go, Elixir, Rust, Python.
Hyperlink scripts per language.
2026-04-30 14:46:41 -07:00
0c51a9334f
fix: patterns mode spec now matches original quality bar
...
Each entry: source hyperlink, real code, why (force), triggers,
before/after examples, over-application warning, decision tree.
Quality bar: 40-80 lines/pattern, 500-900 lines/topic, 5-10K total.
2026-04-30 14:21:56 -07:00
04734c2175
fix: source references hyperlinked to forge (commit SHA + line)
2026-04-30 13:35:17 -07:00
c2f157c5db
fix: patterns mode is iterative — keep extracting until done
...
Process: Discovery → Deepening → Edge cases → Cross-reference.
Repeat until scanning yields no new patterns.
Target: 50-200+ patterns for a language stdlib, 15+ per topic.
2026-04-30 13:33:43 -07:00
03a499e11f
fix: patterns mode requires both 'When to use' and 'When NOT to use'
2026-04-30 13:30:00 -07:00
1711d78eae
feat: dual-mode — conventions (descriptive) OR patterns (prescriptive)
...
Same phases 1-7, diverge at Phase 8 synthesis:
- conventions: how does this project work? → *-conventions repo
- patterns: how should I write code? → *-patterns repo
Patterns mode produces patterns/<topic>.md + smells.md with
prescriptive rules, real examples, and when-NOT-to-use.
2026-04-30 13:20:45 -07:00
886a4d8b46
fix: fully forge-agnostic — no gitea/github references
2026-04-30 12:05:42 -07:00
fd5e0aef53
fix: description consistency — 'git repos' not 'Gitea repos'
2026-04-30 12:03:54 -07:00
8a05b37a50
docs: configuration table with defaults and TOOLS.md example
2026-04-30 12:01:40 -07:00
6df0e383bc
refactor: parameterize environment — no hardcoded paths
...
Configuration (CLONE_DIR, CLONE_HOST, GIT_REMOTE, GIT_ORG, GIT_TOKEN_PATH)
provided by invoker's workspace context. Commands reference shows
Gitea + GitHub examples.
2026-04-30 12:00:09 -07:00
946119a3cc
refactor: skill v2 — thinking frameworks, NEVER list, fallbacks
...
Evaluated via skill-judge: 106/120 (B grade).
- Thinking framework before analysis
- Prioritization criteria (what's worth digging into)
- 10-item NEVER list from 5-repo experience
- Commands externalized to references/commands.md
- Fallbacks for edge cases (no PRs, private repos, young repos)
- Each phase teaches what matters, not how to grep
2026-04-30 11:56:54 -07:00
38a9d66072
feat: codebase-analysis skill
...
8-phase methodology for extracting architectural conventions from
open source repositories:
1. Clone & Shape — measure repo dimensions
2. Import Hierarchy — find foundational packages
3. Interface Contracts — key abstractions
4. Error Handling & Quality Markers — TODOs, style
5. Unique Patterns — project-specific infrastructure
6. Git Archaeology — trace WHY decisions were made
7. PR Discussions — read the actual debates
8. Synthesis — produce analysis.md + conventions.md
Includes pattern-breaks reference (4 categories of why
conventions are violated, with real examples from CockroachDB,
Prometheus, Temporal, Ecto, Oban).
Output: Gitea repos named <project>-conventions.
2026-04-30 11:49:40 -07:00
Rodin