ruby-maat 1.0.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eb9765769289bffda3972bb5e38c0f447c57266d811e29751b08c4c4b2dfe7c1
-  data.tar.gz: d3f8a816d384207f2f47dc03b7d1d912ab073a874ba7e3c8508882bf367c058b
+  metadata.gz: 6015693182fa71b7676389768560ffe75b15b8cc789878a8de2897a4c1e35535
+  data.tar.gz: 7074ca652d6e29ef33502c92769c2ed55f74453c4478a40a401ddd36c3718492
 SHA512:
-  metadata.gz: bb422d1872d9ee5016c08ada681798cb4113ee00dc6a33d357157a5fee4e3c7e319a9ac90ed9e43da6cde80a9136f373642b8e4a467ff3f6ee0326e4b9bac62c
-  data.tar.gz: c343edcaafdaeaca4b348dcc4b643e1bd69000034c3a7be4f7d14345755626eb7d7227276b3f4495ccf1d87891857ffb360735938bace0ccfe643ea0f0d82b4d
+  metadata.gz: e398056d4b83287eb1e926603986243a33005856fb1755d22fadbd1ac14cbb41b9ed1238edbf47033c2164f9a526a74f47b313587abd634063dded3639918330
+  data.tar.gz: fcc96417f9165035d40b7f584a3a9da06234b6e579a505b82678f7da0ce50cb8b74c99da151fdd52d43257f1a82395b109e9ff99fae3f937f8a91f553a313e17

data/.commitlintrc.json

@@ -29,7 +29,8 @@
         "grouper",
         "core",
         "deps",
-        "ci"
+        "ci",
+        "main"
       ]
     ],
     "scope-empty": [0, "never"],

data/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "1.0.0"
+  ".": "1.2.0"
 }

data/.rubocop.yml

@@ -3,12 +3,17 @@ inherit_gem:
   standard: config/base.yml
 
 plugins:
+  - rubocop-performance
   - rubocop-rake
   - rubocop-rspec
 
 AllCops:
   TargetRubyVersion: 3.2
   NewCops: enable
+  Exclude:
+    - 'codeql-repo/**/*'
+    - 'ruby-maat-codeql-db*/**/*'
+    - 'vendor/**/*'
 
 # Project-specific overrides
 Metrics/MethodLength:
@@ -45,4 +50,21 @@ RSpec/MultipleExpectations:
   Max: 25
 
 RSpec/NestedGroups:
-  Max: 5
+  Max: 5
+
+# Allow integration tests to use descriptive names instead of method names
+RSpec/DescribeMethod:
+  Exclude:
+    - "spec/integration/**/*"
+    - "spec/ruby_maat/generators/analysis_integration_spec.rb"
+
+# Allow integration tests to use custom file naming patterns
+RSpec/SpecFilePathFormat:
+  Exclude:
+    - "spec/integration/**/*"
+    - "spec/ruby_maat/generators/analysis_integration_spec.rb"
+
+# Allow instance variables in complex integration tests that need directory management
+RSpec/InstanceVariable:
+  Exclude:
+    - "spec/integration/**/*"

data/.standard.yml

@@ -0,0 +1,3 @@
+ignore:
+  - 'codeql-repo/**/*'
+  - 'ruby-maat-codeql-db*/**/*'

data/CHANGELOG.md

@@ -5,6 +5,106 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.2.0](https://github.com/viamin/ruby-maat/compare/ruby-maat-v1.1.3...ruby-maat/v1.2.0) (2025-08-17)
+
+
+### Features
+
+* add CodeQL security analysis script and update configuration to exclude CodeQL artifacts ([d020fea](https://github.com/viamin/ruby-maat/commit/d020fea2485b456747f3546a6c6f59a8b31b63c4))
+* add interactive log generation mode and enhance log generation options ([2375f04](https://github.com/viamin/ruby-maat/commit/2375f04625f2d101cb48b477728da45249e1f972))
+* add rubocop-performance gem and improve shell command security with validation and escaping ([66f9791](https://github.com/viamin/ruby-maat/commit/66f97917bd4d57da7ce89e6eebbac28dd0326175))
+
+
+### Bug Fixes
+
+* 71 by documenting the format of the mapping files used for architectural analyses ([587f9d0](https://github.com/viamin/ruby-maat/commit/587f9d06e0cad5b9cb14c06aafdfe649870c9d5a))
+* add missing ruby version file to extra-files in release config ([d565352](https://github.com/viamin/ruby-maat/commit/d56535266542396b9a124516ae3c5de1fb3926f5))
+* add release-commit-message-scope configuration for CI ([59f1af1](https://github.com/viamin/ruby-maat/commit/59f1af1837cec33bed85f7a11bf0d56c9edb0a29))
+* add release-commit-message-scope configuration for CI ([e580a05](https://github.com/viamin/ruby-maat/commit/e580a05c489d8a393c75d199ed01191591d84574))
+* improve shell command execution and regex pattern for change detection ([0566796](https://github.com/viamin/ruby-maat/commit/05667963965cc137a3343ca492ffc1bf81791c37))
+* update CHANGE_PATTERN regex for improved line matching in Git2Parser ([3ffc27c](https://github.com/viamin/ruby-maat/commit/3ffc27c4abde42494daff8f701aa38c1dffbb1eb))
+* update permissions in CI workflows for better access control ([9c30839](https://github.com/viamin/ruby-maat/commit/9c30839ea3c8f6c7fee56d911231ebc27faa35df))
+* update permissions in CI workflows for better access control ([be49302](https://github.com/viamin/ruby-maat/commit/be49302c98a16b528ebf56137667998382ce56c4))
+* update regex patterns in parsers for improved matching ([d56ef8f](https://github.com/viamin/ruby-maat/commit/d56ef8fb93a433ffbafd74374966271bd6419ebc))
+* version info for automations ([6d1dc43](https://github.com/viamin/ruby-maat/commit/6d1dc43f1b3bf666ca54b7d3c5999d63a7964cab))
+
+
+### CI/CD
+
+* **deps:** bump actions/checkout from 4 to 5 ([ab5ceac](https://github.com/viamin/ruby-maat/commit/ab5ceac8a3d6c633efa309bd58d355b3489afb4f))
+* **deps:** bump codecov/codecov-action from 4 to 5 ([9b3c1dd](https://github.com/viamin/ruby-maat/commit/9b3c1dd4bb93fd024bd6a9c22160f602f4811391))
+
+
+### Documentation
+
+* Update README.md for on-prem pricing page ([e745abe](https://github.com/viamin/ruby-maat/commit/e745abece16b47adbb18d63fdaba39eb31c69204))
+
+
+### Refactoring
+
+* put a new on the complex behavior for organizing commits into sliding windows ([4829229](https://github.com/viamin/ruby-maat/commit/48292293652912af17835e1f31190ff720882dc2))
+* Ruby Maat for Enhanced Log Generation and CLI Features ([de6123e](https://github.com/viamin/ruby-maat/commit/de6123ee827376d18ac8cd62a25da50debd755d7))
+* Ruby Maat for Enhanced Log Generation and CLI Features ([e5a6410](https://github.com/viamin/ruby-maat/commit/e5a64105b45e88c89ccdb074befa9ece453666ea))
+* update RSpec configuration and improve integration test handling ([b6895cb](https://github.com/viamin/ruby-maat/commit/b6895cb7e6ad9e1d53f836e1f7472a719372bd86))
+* update RSpec tests to use `described_class` and improve mock handling ([033dbe3](https://github.com/viamin/ruby-maat/commit/033dbe3c483041f249f12f500fb7483447902fe0))
+
+
+### Miscellaneous
+
+* add extra-files configuration for version file in release-please ([2a1ae29](https://github.com/viamin/ruby-maat/commit/2a1ae29f1c898b78e426cc6c9c23340ea573e87e))
+* **main:** release 1.1.0 ([befebb9](https://github.com/viamin/ruby-maat/commit/befebb9d2522d01b8cc6962b2ed43a3ba7507e4c))
+* **main:** release 1.1.0 ([8160a68](https://github.com/viamin/ruby-maat/commit/8160a6836b063603b05bb0a81297ecb1d4cb29f5))
+* **main:** release 1.1.1 ([a435b9c](https://github.com/viamin/ruby-maat/commit/a435b9ca99ffe79e89d5c5f378cf638930104a77))
+* **main:** release 1.1.1 ([eb74e48](https://github.com/viamin/ruby-maat/commit/eb74e486ca7e750c72bb88edec4354c3f2239cc6))
+* **main:** release 1.1.2 ([f3d6842](https://github.com/viamin/ruby-maat/commit/f3d6842d4a76fcaafdd7adc628c968174f616d6c))
+* **main:** release 1.1.2 ([4535251](https://github.com/viamin/ruby-maat/commit/45352512ed80c992f9a9ecdab10513055e38a1d4))
+* **main:** release 1.1.3 ([8bad82f](https://github.com/viamin/ruby-maat/commit/8bad82f5822aa1ef5f40f7a249dd30d449b69f4f))
+* **main:** release 1.1.3 ([5a6552f](https://github.com/viamin/ruby-maat/commit/5a6552fd4e3a64b74dab6b075196573b3599fdf6))
+* update CI workflows to include concurrency settings and adjust version to 1.1.2 ([a21698e](https://github.com/viamin/ruby-maat/commit/a21698e7bf49a2b4ee7a47e2311379ce60e5271a))
+* update commitlint configuration and add Overcommit setup; implement commit message validation script ([890f3f5](https://github.com/viamin/ruby-maat/commit/890f3f519c564d0dd60990a22d844f203980959b))
+* update GitHub Actions workflow for release process; add permissions and release type configuration ([e5dca27](https://github.com/viamin/ruby-maat/commit/e5dca27e32efa43f0ab677cd96e7cc2b56ce6fb0))
+* update release configuration by removing inline settings and adding dedicated config file ([240ba2a](https://github.com/viamin/ruby-maat/commit/240ba2a7962d1bb286a79d4b3c63199053037b95))
+* update ruby-maat version to 1.1.2 in Gemfile.lock ([bf5bfa7](https://github.com/viamin/ruby-maat/commit/bf5bfa7e996a82af23c40acd70236774026b7cde))
+
+## [1.1.3](https://github.com/viamin/ruby-maat/compare/v1.1.2...v1.1.3) (2025-08-17)
+
+
+### Bug Fixes
+
+* add missing ruby version file to extra-files in release config ([d565352](https://github.com/viamin/ruby-maat/commit/d56535266542396b9a124516ae3c5de1fb3926f5))
+
+## [1.1.2](https://github.com/viamin/ruby-maat/compare/v1.1.1...v1.1.2) (2025-08-17)
+
+
+### Bug Fixes
+
+* update permissions in CI workflows for better access control ([9c30839](https://github.com/viamin/ruby-maat/commit/9c30839ea3c8f6c7fee56d911231ebc27faa35df))
+* update permissions in CI workflows for better access control ([be49302](https://github.com/viamin/ruby-maat/commit/be49302c98a16b528ebf56137667998382ce56c4))
+
+## [1.1.1](https://github.com/viamin/ruby-maat/compare/v1.1.0...v1.1.1) (2025-08-16)
+
+
+### Bug Fixes
+
+* add release-commit-message-scope configuration for CI ([59f1af1](https://github.com/viamin/ruby-maat/commit/59f1af1837cec33bed85f7a11bf0d56c9edb0a29))
+* add release-commit-message-scope configuration for CI ([e580a05](https://github.com/viamin/ruby-maat/commit/e580a05c489d8a393c75d199ed01191591d84574))
+
+## [1.1.0](https://github.com/viamin/ruby-maat/compare/v1.0.0...v1.1.0) (2025-08-16)
+
+
+### Features
+
+* add CodeQL security analysis script and update configuration to exclude CodeQL artifacts ([d020fea](https://github.com/viamin/ruby-maat/commit/d020fea2485b456747f3546a6c6f59a8b31b63c4))
+* add interactive log generation mode and enhance log generation options ([2375f04](https://github.com/viamin/ruby-maat/commit/2375f04625f2d101cb48b477728da45249e1f972))
+* add rubocop-performance gem and improve shell command security with validation and escaping ([66f9791](https://github.com/viamin/ruby-maat/commit/66f97917bd4d57da7ce89e6eebbac28dd0326175))
+
+
+### Bug Fixes
+
+* improve shell command execution and regex pattern for change detection ([0566796](https://github.com/viamin/ruby-maat/commit/05667963965cc137a3343ca492ffc1bf81791c37))
+* update CHANGE_PATTERN regex for improved line matching in Git2Parser ([3ffc27c](https://github.com/viamin/ruby-maat/commit/3ffc27c4abde42494daff8f701aa38c1dffbb1eb))
+* update regex patterns in parsers for improved matching ([d56ef8f](https://github.com/viamin/ruby-maat/commit/d56ef8fb93a433ffbafd74374966271bd6419ebc))
+
 ## [1.0.0] - 2024-08-15
 
 ### Added

data/CLAUDE.md

@@ -4,84 +4,112 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-Code Maat is a command-line tool for mining and analyzing data from version control systems (VCS). It extracts insights about code evolution, developer patterns, logical coupling, and code quality metrics from Git, SVN, Mercurial, Perforce, and TFS repositories.
+Ruby Maat is a Ruby port of Code Maat - a command-line tool for mining and analyzing data from version control systems (VCS). It extracts insights about code evolution, developer patterns, logical coupling, and code quality metrics from Git, SVN, Mercurial, Perforce, and TFS repositories.
+
+**Key Feature**: Ruby Maat includes built-in log generation capabilities, allowing users to generate VCS logs directly without requiring external shell commands.
 
 ## Build and Development Commands
 
 ### Building the Project
 
 ```bash
-# Build standalone JAR (primary method)
-lein uberjar
-
-# Run directly via Leiningen (for development)
-lein run -l logfile.log -c <vcs>
+# Install dependencies
+bundle install
 
-# Build Docker image
-docker build -t code-maat-app .
+# Build gem
+gem build ruby-maat.gemspec
 
 # Run tests
-lein test
+bundle exec rspec
 ```
 
-### Running Code Maat
+### Running Ruby Maat
 
 ```bash
-# Using standalone JAR
-java -jar code-maat-1.0.5-SNAPSHOT-standalone.jar -l logfile.log -c <vcs>
+# Run analysis on existing log file
+ruby-maat -l logfile.log -c git -a authors
+
+# Generate log file and save for future use
+ruby-maat --generate-log --save-log my_log.log -c git
+
+# Generate log and run analysis immediately
+ruby-maat --generate-log -c git -a coupling
 
-# Using Docker
-docker run -v /host/path:/data -it code-maat-app -l /data/logfile.log -c <vcs>
+# Interactive log generation
+ruby-maat --generate-log --interactive -c git
+
+# Use preset configurations
+ruby-maat --generate-log --preset git2-format -c git
 
 # Show help and all available analyses
-java -jar code-maat-1.0.5-SNAPSHOT-standalone.jar -h
+ruby-maat -h
 ```
 
-### Memory Configuration
+### Log Generation
+
+Ruby Maat can generate VCS logs directly, eliminating the need for manual log extraction:
 
-Code Maat is memory-intensive. The project.clj includes these JVM options:
+**Available Presets:**
+- `git2-format` - Standard format for git2 parser (recommended)
+- `git-legacy` - Legacy format for git parser
+- `recent-activity` - Last 3 months of activity
+- `last-year` - Last 12 months of activity
+- `full-history` - Complete repository history
 
-- `-Xmx4g` (4GB heap)
-- `-Djava.awt.headless=true` (suppress AWT frames)
-- `-Xss512M` (512MB stack size)
+**Supported VCS for Log Generation:**
+- Git (both git and git2 formats)
+- SVN (XML format)
+
+**Interactive Mode Features:**
+- Preset selection
+- Custom date filtering
+- Author filtering
+- Path filtering
+- Save or temporary log options
 
 ## Architecture Overview
 
 ### Core Components
 
-1. **Command Line Interface** (`src/code_maat/cmd_line.clj`)
+1. **Command Line Interface** (`lib/ruby_maat/cli.rb`)
    - Entry point and argument parsing
-   - Uses clojure.tools.cli for option handling
+   - Uses OptionParser for option handling
+   - Handles both analysis and log generation modes
 
-2. **Application Core** (`src/code_maat/app/app.clj`)
+2. **Application Core** (`lib/ruby_maat/app.rb`)
    - Main orchestration logic following pipeline pattern:
-     - Input → Parsers → Layer Mapping → Incanter Datasets → Analysis → Output
+     - Input → Parsers → Layer Mapping → Datasets → Analysis → Output
    - Contains registry of all supported analyses
    - Handles VCS parser selection and error recovery
 
-3. **VCS Parsers** (`src/code_maat/parsers/`)
+3. **VCS Parsers** (`lib/ruby_maat/parsers/`)
    - Modular parsers for different VCS systems
-   - `git2.clj` - preferred Git parser (faster, more tolerant)
-   - `git.clj` - legacy Git parser (maintained for backward compatibility)
-   - `svn.clj`, `mercurial.clj`, `perforce.clj`, `tfs.clj` - other VCS support
+   - `git2_parser.rb` - preferred Git parser (faster, more tolerant)
+   - `git_parser.rb` - legacy Git parser (maintained for backward compatibility)
+   - `svn_parser.rb`, `mercurial_parser.rb`, `perforce_parser.rb`, `tfs_parser.rb` - other VCS support
+
+4. **Log Generators** (`lib/ruby_maat/generators/`) - **NEW FEATURE**
+   - `base_generator.rb` - common functionality for all generators
+   - `git_generator.rb` - Git log generation with presets and interactive mode
+   - `svn_generator.rb` - SVN log generation with XML output
+   - Support for preset configurations and custom options
 
-4. **Analysis Modules** (`src/code_maat/analysis/`)
+5. **Analysis Modules** (`lib/ruby_maat/analysis/`)
    - Independent analysis implementations
-   - Each returns Incanter datasets
    - Key analyses: authors, coupling, churn, code-age, communication, effort
 
-5. **Data Processing** (`src/code_maat/app/`)
-   - `grouper.clj` - maps files to architectural layers
-   - `time_based_grouper.clj` - temporal aggregation
-   - `team_mapper.clj` - maps authors to teams
+6. **Data Processing** (`lib/ruby_maat/groupers/`)
+   - `layer_grouper.rb` - maps files to architectural layers
+   - `time_grouper.rb` - temporal aggregation
+   - `team_mapper.rb` - maps authors to teams
 
-6. **Output** (`src/code_maat/output/`)
+7. **Output** (`lib/ruby_maat/output/`)
    - CSV output formatting
    - Filtering and row limiting
 
 ### Supported Analyses
 
-Available via the `-a` parameter (see `supported-analysis` map in `app.clj:55`):
+Available via the `-a` parameter (see `SUPPORTED_ANALYSES` in `app.rb`):
 
 - `authors` - developer count per module
 - `coupling` - logical coupling between modules  
@@ -94,37 +122,59 @@ Available via the `-a` parameter (see `supported-analysis` map in `app.clj:55`):
 
 ### Data Flow
 
+**Traditional Mode (with existing logs):**
 1. Parse VCS log files into modification records
 2. Optional aggregation by architectural boundaries (grouping files)
 3. Optional temporal aggregation (group commits by time period)
 4. Optional team mapping (map individual authors to teams)
-5. Convert to Incanter dataset
+5. Convert to dataset
 6. Run analysis
 7. Output results as CSV
 
+**Log Generation Mode (NEW):**
+1. Generate VCS log using appropriate generator
+2. Either save log to file for future use, or pipe directly to analysis
+3. Follow traditional data flow for analysis
+
 ### Key Dependencies
 
-- Clojure 1.8.0
-- Incanter (statistical computing)
-- clojure.tools.cli (command line parsing)
-- clj-time (date/time handling)
-- instaparse (parsing DSL)
+- Ruby 2.7+
+- Standard Ruby libraries (optparse, date, fileutils, etc.)
+- RSpec (for testing)
 
 ## Testing
 
-Tests are located in `test/code_maat/` and follow the source structure. Key test categories:
+Tests are located in `spec/` and follow the source structure. Key test categories:
 
 - Unit tests for individual analysis modules
-- End-to-end scenario tests with sample VCS data
 - Parser tests for different VCS formats
+- Log generator tests with mocked VCS repositories
+- CLI integration tests
 
-Run all tests with `lein test`.
+Run all tests with `bundle exec rspec`.
 
 ## Development Notes
 
-- The codebase follows functional programming principles
+- The codebase follows object-oriented Ruby principles with functional influences
 - All analysis modules are independent and composable  
-- Parsers return sequences of maps representing modifications
-- Heavy use of Incanter for dataset operations
-- Error handling with recovery points for user-friendly messages
-- Memory usage can be high for large repositories - consider date filtering
+- Parsers return arrays of ChangeRecord objects representing modifications
+- Log generators use command execution with proper error handling
+- Interactive mode provides user-friendly prompts and validation
+- Memory usage can be high for large repositories - use date filtering presets
+- Log generation supports both persistent and temporary modes for different workflows
+
+## Log Generation Examples
+
+```bash
+# Quick analysis of recent Git activity
+ruby-maat --generate-log --preset recent-activity -c git -a authors
+
+# Interactive SVN log generation with custom options
+ruby-maat --generate-log --interactive -c svn
+
+# Generate and save Git log for later analysis
+ruby-maat --generate-log --save-log project_history.log --preset full-history -c git
+
+# Generate log and immediately run coupling analysis
+ruby-maat --generate-log -c git -a coupling --min-revs 10
+```

data/README.md

@@ -4,18 +4,21 @@ Ruby Maat is a command line tool used to mine and analyze data from version-cont
 
 **Note:** The analyses have evolved into [CodeScene](https://codescene.io/), which automates all the analyses found in Ruby Maat and several new ones.
 
-## Drop-in Replacement for Code Maat
+## Drop-in Replacement for Code Maat + Log Generation
 
-Ruby Maat is designed as a **drop-in replacement** for the original Code Maat. It supports:
+Ruby Maat is designed as a **drop-in replacement** for the original Code Maat with enhanced capabilities:
 
 - ✅ Identical command-line arguments
 - ✅ Same VCS log file formats*
 - ✅ Compatible CSV output format
 - ✅ All original analysis types
+- 🆕 **Built-in log generation** - No need for manual VCS commands
+- 🆕 **Interactive mode** with guided log creation
+- 🆕 **Preset configurations** for common scenarios
 
 `*` In theory. I've only tested with git.
 
-Simply replace `java -jar code-maat.jar` with `ruby-maat` in your existing scripts.
+Simply replace `java -jar code-maat.jar` with `ruby-maat` in your existing scripts, or use the new log generation features for a streamlined workflow.
 
 ## Installation
 
@@ -29,7 +32,12 @@ gem install ruby-maat
 
 ```bash
 docker build -t ruby-maat .
+
+# Traditional mode with existing logs
 docker run -v /path/to/your/logs:/data ruby-maat -l /data/logfile.log -c git2 -a summary
+
+# NEW: Log generation mode (mount your repository)
+docker run -v /path/to/your/repo:/repo ruby-maat --generate-log --preset recent-activity -c git -a coupling
 ```
 
 ### From Source
@@ -54,6 +62,7 @@ Distributed under the [GNU General Public License v3.0](http://www.gnu.org/licen
 
 ### Basic Usage
 
+#### Traditional Mode (with existing logs)
 ```bash
 # Analyze Git repository
 ruby-maat -l logfile.log -c git2 -a summary
@@ -65,16 +74,42 @@ ruby-maat -l logfile.log -c git2 -a coupling
 ruby-maat -l logfile.log -c git2 -a authors -o results.csv
 ```
 
+#### New: Log Generation Mode
+```bash
+# Generate log and analyze immediately
+ruby-maat --generate-log -c git -a authors
+
+# Generate log with preset and save for later
+ruby-maat --generate-log --preset recent-activity --save-log my_log.log -c git
+
+# Interactive mode with guided setup
+ruby-maat --generate-log --interactive -c git
+
+# Generate log and run specific analysis
+ruby-maat --generate-log --preset git2-format -c git -a coupling --min-revs 10
+```
+
 ### Command Line Options
 
 When invoked with `-h`, Ruby Maat prints its usage:
 
 ```
-Usage: ruby-maat -l log-file -c vcs-type [options]
+Usage: 
+  ruby-maat -l log-file -c vcs-type [options]           # Run analysis on existing log
+  ruby-maat --generate-log -c vcs-type [options]        # Generate log file
+  ruby-maat --generate-log --interactive -c vcs-type    # Interactive log generation
 
 Required:
-  -l, --log LOG                    Log file with input data
   -c, --version-control VCS        Input vcs module type: supports svn, git, git2, hg, p4, or tfs
+  -l, --log LOG                    Log file with input data (not required with --generate-log)
+
+Log Generation (NEW):
+      --generate-log               Generate log file instead of running analysis
+      --save-log FILENAME          Save generated log to file
+      --interactive                Use interactive mode for log generation
+      --preset PRESET              Use a preset configuration for log generation
+                                   Git presets: git2-format, git-legacy, recent-activity, last-year, full-history
+                                   SVN presets: standard, recent-activity, last-year, date-range, revision-range
 
 Analysis:
   -a, --analysis ANALYSIS          The analysis to run (default: authors)
@@ -102,7 +137,53 @@ Other:
 
 ### Generating input data
 
-Ruby Maat operates on log files from version-control systems. **Use the exact same commands as the original Code Maat.** The supported version-control systems are `git`, Mercurial (`hg`), `svn`, Perforce (`p4`), and Team Foundation Server (`tfs`). The log files are generated by using the version-control systems themselves as described in the following sections.
+Ruby Maat operates on log files from version-control systems. You have **two options**:
+
+1. **🆕 NEW: Automatic log generation** - Ruby Maat can generate logs for you
+2. **Traditional: Manual log generation** - Use VCS commands directly (same as original Code Maat)
+
+#### Option 1: Automatic Log Generation (Recommended)
+
+Ruby Maat can generate VCS logs automatically with built-in presets and interactive guidance:
+
+```bash
+# Quick start - analyze recent Git activity
+ruby-maat --generate-log --preset recent-activity -c git -a summary
+
+# Interactive mode with guided setup
+ruby-maat --generate-log --interactive -c git
+
+# Generate and save SVN log for later use
+ruby-maat --generate-log --preset standard --save-log svn_history.log -c svn
+```
+
+**Available Presets:**
+
+**Git Presets:**
+- `git2-format` - Standard format for git2 parser (recommended)
+- `git-legacy` - Legacy format for git parser  
+- `recent-activity` - Last 3 months of activity
+- `last-year` - Last 12 months of activity
+- `full-history` - Complete repository history
+
+**SVN Presets:**
+- `standard` - Standard SVN XML log format
+- `recent-activity` - Last 3 months of activity
+- `last-year` - Last 12 months of activity
+- `date-range` - Custom date range (interactive)
+- `revision-range` - Specific revision range (interactive)
+
+**Interactive Mode Features:**
+- Preset selection with descriptions
+- Custom date filtering (YYYY-MM-DD format)
+- Author filtering
+- Path filtering  
+- Branch selection (Git)
+- Save or temporary log options
+
+#### Option 2: Manual Log Generation (Traditional)
+
+For compatibility with existing workflows, you can still generate logs manually. **Use the exact same commands as the original Code Maat.** The supported version-control systems are `git`, Mercurial (`hg`), `svn`, Perforce (`p4`), and Team Foundation Server (`tfs`).
 
 #### Preparations
 
@@ -159,15 +240,25 @@ To exclude multiple folders, you just append more pathspecs:
 
 ### Running Ruby Maat
 
+#### Traditional Mode (with existing logs)
+
 If you've installed the gem:
 
        ruby-maat -l logfile.log -c <vcs>
 
-If you've built a docker container, then you can run it as
+If you've built a docker container:
 
         docker run -v /home/xx/src/logs:/data -it ruby-maat -l /data/logfile.log -c <vcs>
 
-where the /home/xx/src/logs is the host's directory containing the file logfile.log.
+#### NEW: Log Generation Mode
+
+Generate logs automatically:
+
+       ruby-maat --generate-log -c <vcs> -a <analysis>
+
+With Docker (mount your repository):
+
+        docker run -v /path/to/repo:/repo -it ruby-maat --generate-log -c <vcs> -a <analysis>
 
 When invoked with `-h`, Ruby Maat prints its usage. (See the [Command Line Options](#command-line-options) section above for details.)
 

data/lib/ruby_maat/analysis/churn.rb

@@ -105,7 +105,7 @@ module RubyMaat
           end
 
           # Filter by minimum revisions and format results
-          filtered_results = results.values.map do |result|
+          filtered_results = results.values.filter_map do |result|
             next if result[:revisions].size < min_revs
 
             {
@@ -114,7 +114,7 @@ module RubyMaat
               deleted: result[:deleted],
               commits: result[:revisions].size
             }
-          end.compact
+          end
 
           # Sort by total churn descending
           filtered_results.sort_by! { |r| -(r[:added] + r[:deleted]) }

data/lib/ruby_maat/analysis/effort.rb

@@ -76,13 +76,13 @@ module RubyMaat
           results = []
 
           entity_authors.each do |entity, authors|
-            total_revisions = authors.values.map(&:size).sum
+            total_revisions = authors.values.sum(&:size)
             next if total_revisions < min_revs
 
             # Find author with most revisions
             main_author, revisions = authors.max_by { |_author, revs| revs.size }
 
-            total_revisions = authors.values.map(&:size).sum
+            total_revisions = authors.values.sum(&:size)
 
             results << {
               entity: entity,
@@ -122,14 +122,14 @@ module RubyMaat
           results = []
 
           entity_contributions.each do |entity, authors|
-            total_revisions = authors.values.map(&:size).sum
+            total_revisions = authors.values.sum(&:size)
             next if total_revisions < min_revs
 
             # Calculate fractal value: 1 - sum(p_i^2) where p_i is proportion of each author
-            sum_of_squares = authors.values.map do |revisions|
+            sum_of_squares = authors.values.sum do |revisions|
               proportion = revisions.size.to_f / total_revisions
               proportion**2
-            end.sum
+            end
 
             fractal_value = 1.0 - sum_of_squares