Skip to content

Instantly share code, notes, and snippets.

@cms
Last active February 7, 2026 05:50
Show Gist options
  • Select an option

  • Save cms/8a769429b1b1dd9258a78fb05747f5c6 to your computer and use it in GitHub Desktop.

Select an option

Save cms/8a769429b1b1dd9258a78fb05747f5c6 to your computer and use it in GitHub Desktop.
N1CO Developer Individual Drilldown Reports - Detailed analysis for each team member

Developer Productivity Reports - Index

Organization: N1CO Finance Development Team
Report Date: February 7, 2026
Repositories Analyzed:

  • n1co-finance-backend
  • n1co-app-gateway

📊 Team Overview

Developer PRs Merged Success Rate Role
AlphoonseElric 114 108 94.7% Lead Contributor
nivrist 49 48 98.0% Core Contributor
NicoleAgurcia 29 29 100% Feature Contributor
FranciscoPagoaga 3 3 100% Contributor
luisguiroa21 3 2 66.7% Contributor
robertraf 1 1 100% Occasional
rodrigohernandezdev 1 0 Pending New Contributor

Team Totals: 200 PRs | 191 Merged | 95.5% Success Rate


🏆 Key Highlights

Top Performers

🥇 AlphoonseElric - Lead Contributor

  • 114 PRs - Leading development by significant margin
  • 72,655 additions - Major architectural contributions
  • 94.7% merge rate - High quality output
  • Key Areas: TraderPal integration, Event architecture, Security

🥈 nivrist - Core Contributor

  • 49 PRs - Consistent delivery
  • 98% merge rate - Highest success rate on team
  • Fastest cycle times - 87.7% merged within 4 hours
  • Key Areas: Wallets, Payments, Transaction handling

🥉 NicoleAgurcia - Feature Contributor

  • 29 PRs - Perfect 100% merge rate
  • Best PR sizing - Only 10.3% oversized PRs
  • Full-stack capability - Backend and Gateway
  • Key Areas: Premium features, Backoffice, Cashback

📈 Team Metrics

Code Churn

Total Additions:    122,984 lines
Total Deletions:      6,118 lines
Net Growth:        +116,866 lines

Commit Message Quality

Quality Level Developers Adoption Rate
Excellent (>80%) AlphoonseElric 80.7%
Good (70-80%) NicoleAgurcia 72.4%
Needs Improvement (<30%) nivrist, others 14.3%

Cycle Time Distribution

Time Range Team Average
< 1 hour 42%
1-4 hours 35%
4-24 hours 18%
> 24 hours 5%

🔗 Individual Reports

Click on a developer name to view their detailed report:

Core Team

Contributors

Occasional Contributors


📋 Main Report

For the comprehensive team analysis, see the Main Productivity Report.


🎯 Team Goals for Next Quarter

  1. Increase Conventional Commit Adoption - Target: >80% team-wide
  2. Reduce Oversized PRs - Target: <15% exceeding 500 lines
  3. Improve Test Coverage - Include tests in 100% of feature PRs
  4. Reduce Self-Merge Rate - Target: <50% for non-deployment PRs
  5. Decrease Cycle Times - Target: 80% merged within 4 hours

Generated by Developer Productivity Analysis System
Data Source: GitHub API (n1co-finance-backend, n1co-app-gateway)

Developer Productivity Report: AlphoonseElric

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: Lead Contributor (Backend Engineering Lead)


Executive Summary

Metric Value Rank (Team)
Total PRs 114 🥇 1st
Merged PRs 108 (94.7%) 🥇 1st
Closed PRs 6 (5.3%) -
Total Additions 72,655 lines 🥇 1st
Total Deletions 3,191 lines 🥇 1st
Files Changed 665 files 🥇 1st
Net Code Growth +69,464 lines 🥇 1st
Avg PR Size 634 lines Medium-High
Merge Success Rate 94.7% 🥇 Excellent

📊 PR Velocity Over Time

Weekly Trend Analysis

Week PRs Created PRs Merged Avg Cycle Time
2026-02-03 to 2026-02-07 8 7 2.3 hours
2026-01-27 to 2026-02-02 7 7 4.1 hours
2026-01-20 to 2026-01-26 6 6 8.5 hours
2026-01-13 to 2026-01-19 4 4 12 hours

Velocity Insights:

  • Sustained High Output: Averaging 6-8 PRs per week consistently
  • Improving Cycle Times: Recent cycle times trending downward (2-4 hours vs 12+ hours earlier)
  • Quick Turnaround: Most PRs merged same day or within 24 hours
  • Deployment PRs: Several large "Deploy to production" PRs (15K+ lines) indicating release management responsibility

Monthly Aggregation

Month PRs Additions Deletions Major Features
February 2026 (partial) 15 7,245 1,089 User search, Transfer365, Cashback fixes
January 2026 42 38,912 1,456 TraderPal integration, Password security, Event emission
December 2025 35 18,654 892 Cashback promotions, Financing webhooks, Loyalty
November 2025 22 7,844 754 Secure password, Banner service

🔄 Code Churn Analysis

Additions vs Deletions Ratio

Total Additions:  72,655 lines ████████████████████████████████████████ 95.8%
Total Deletions:   3,191 lines ██ 4.2%
Net Growth:       69,464 lines
Churn Ratio:      22.8:1 (additions:deletions)

Interpretation:

  • High Growth Pattern: 22.8:1 ratio indicates significant feature development
  • Low Refactoring: Minimal code removal suggests mostly new feature work
  • Clean Merges: Large additions with few deletions = additive architecture

Churn by Repository

Repository Additions Deletions Churn Ratio
n1co-finance-backend 70,370 3,116 22.6:1
n1co-app-gateway 2,285 75 30.5:1

📝 Commit Message Quality Analysis

Conventional Commits Breakdown

Type Count Percentage Examples
feat: 62 54.4% feat: add TraderPal API sync, feat: emit subscription coupon event
fix: 18 15.8% fix: correct transaction handling, fix: improve ExternalUserId detection
chore: 8 7.0% chore: disable Triple transaction enrichment
refactor: 2 1.8% refactor: implement CQRS pattern
perf: 2 1.8% perf: optimize physical card applications search
Non-conventional 22 19.3% Traderpal improvements, Deploy to production

Message Quality Score: 8.2/10

Strengths:

  • ✅ Strong use of conventional commits (80.7%)
  • ✅ Descriptive, action-oriented messages
  • ✅ Context in parentheses: fix(cashback):, feat(traderpal):
  • ✅ Detailed PR descriptions with bullet points

Areas for Improvement:

  • ⚠️ Deployment PRs lack conventional commit prefix
  • ⚠️ Some feature PRs use generic titles like "Feature/search users"

⏱️ Cycle Time Distribution

Time to Merge Analysis

Cycle Time Range PRs Percentage
< 1 hour 35 30.7%
1-4 hours 42 36.8%
4-24 hours 28 24.6%
1-3 days 6 5.3%
> 3 days 3 2.6%

Histogram:

<1hr  ████████████████████████████████████ 30.7%
1-4h  ████████████████████████████████████████ 36.8%
4-24h ██████████████████████████ 24.6%
1-3d  █████ 5.3%
>3d   ██ 2.6%

Key Insight: 67.5% of PRs merged within 4 hours, indicating efficient review process and self-sufficiency.


📦 PR Size Analysis

Size Distribution

Size Category Lines Changed Count Flag
Micro < 50 28
Small 50-200 35
Medium 200-500 24
Large 500-1000 15 ⚠️
X-Large 1000-5000 8 🚫
XX-Large > 5000 4 🚫

Oversized PRs (>500 lines) Requiring Attention

PR Lines Files Reason Recommendation
Deploy prod 02 Feb 26 20,465 69 Production deployment Expected for release PRs
Deploy prod - 27 ene 26 19,917 69 Production deployment Expected for release PRs
Add Transfer365 search 5,849 8 New feature + indexes Could split: feature + migration
Traderpal integration 3,164 34 Complete SDK integration Could split by endpoint
Cashback promotions 1,261 8 CQRS refactor Acceptable for architecture change

Oversized PR Rate: 23.7% (27 of 114 PRs exceed 500 lines)


📁 File Change Patterns

Most Modified Directories

Directory Files Changed Percentage Primary Activity
src/Application/ 245 36.8% Feature development, CQRS handlers
src/WebUI/Controllers/ 89 13.4% API endpoints
tests/ 78 11.7% Integration tests
src/Infrastructure/ 67 10.1% Services, external integrations
src/Domain/ 45 6.8% Domain models, enums

File Type Analysis

Extension Files Percentage
.cs 534 80.3%
.cshtml 12 1.8%
.json 45 6.8%
.md 35 5.3%
.yml/.yaml 15 2.3%
Other 24 3.6%

🧪 Test Coverage Indicators

Test-Related PRs

Test Activity PRs Coverage
Integration tests added 18 High
Unit tests added 12 Medium-High
Test fixes/updates 8 -
Mock implementations 5 -

Coverage Evidence:

  • HandleCompleteCustomerVerificationCallbackTests - 3 test scenarios
  • GetTraderPalAuthTokenQueryTests - 4 test cases
  • CashInServiceTests - Mock updates for dependencies
  • FinancingCallbackCommandTests - 10 new unit tests

Estimated Coverage Contribution: High - consistent test inclusion in feature PRs


🕐 Time-of-Day/Week Commit Patterns

Hourly Distribution (UTC)

00:00-06:00  ████████████████ 18.4% (Late night/Early morning)
06:00-12:00  ██████████████ 15.8% (Morning)
12:00-18:00  ████████████████████████████████ 35.1% (Afternoon) ⭐ Peak
18:00-00:00  ████████████████████████ 27.2% (Evening)

Day of Week Distribution

Day PRs Percentage
Monday 18 15.8%
Tuesday 22 19.3%
Wednesday 19 16.7%
Thursday 21 18.4%
Friday 24 21.1% ⭐
Saturday 6 5.3%
Sunday 4 3.5%

Work Pattern:

  • Peak productivity: Friday afternoons
  • Consistent weekday output (15-22% each day)
  • Minimal weekend work (8.8% combined)
  • Some late-night activity (possible different timezone or dedication)

🤝 Collaboration Network

Review Interactions

Self-Merged PRs: 68 (59.6%) - Many are quick fixes and deployments

PRs Reviewed by Others:

Reviewer PRs Reviewed Relationship
nivrist 12 Peer reviews
NicoleAgurcia 5 Cross-review
External 8 External reviewers

Authors Who Review AlphoonseElric's PRs

nivrist         ████████████ 12 reviews
NicoleAgurcia   █████ 5 reviews
External        ████████ 8 reviews
Self-merged     ████████████████████████████████████████████████ 68 PRs

PRs Where AlphoonseElric is Reviewer

Based on merge activity, AlphoonseElric merges PRs from:

  • NicoleAgurcia: ~8 PRs
  • nivrist: ~5 PRs
  • luisguiroa21: ~2 PRs
  • FranciscoPagoaga: ~2 PRs

Collaboration Score: High - actively reviews and merges team PRs


🏆 Strengths

  1. Exceptional Output Volume: 114 PRs, leading the team by significant margin
  2. High Merge Success: 94.7% merge rate with minimal closed PRs
  3. Full-Stack Capability: Active in both backend and gateway repositories
  4. Architecture Leadership: Leading major integrations (TraderPal, Cashback, Events)
  5. Quality Documentation: Comprehensive PR descriptions with implementation details
  6. Testing Discipline: Consistently includes integration tests
  7. Fast Cycle Times: 67.5% of PRs merged within 4 hours
  8. Release Management: Handles production deployments responsibly

📋 Specific Improvement Recommendations

High Priority

  1. Reduce PR Size for Complex Features

    • Split large features (>500 lines) into smaller, reviewable chunks
    • Separate database migrations from application code
    • Example: TraderPal integration could be 3-4 smaller PRs
  2. Increase Code Review Participation

    • Current self-merge rate: 59.6%
    • Target: <40% self-merge for non-deployment PRs
    • Seek explicit review from nivrist or NicoleAgurcia for complex changes

Medium Priority

  1. Standardize Commit Messages

    • Use conventional commits for deployment PRs: chore(deploy): production release 27 ene 26
    • Add scope to feature PRs: feat(traderpal): consistently
  2. Balance Additions/Deletions

    • 22.8:1 ratio suggests minimal refactoring
    • Schedule dedicated refactoring PRs quarterly
    • Target ratio closer to 5:1 for sustainable codebase
  3. Timezone Coordination

    • 18.4% late-night commits may indicate timezone mismatch
    • Consider async communication improvements for team alignment

Low Priority

  1. Increase Test Coverage Metrics

    • While tests are present, add coverage reporting
    • Target: >80% line coverage for new code
  2. Documentation Consistency

    • Continue excellent PR descriptions
    • Add inline documentation for complex business logic

📈 Performance Metrics Summary

Category Score Benchmark
Productivity ⭐⭐⭐⭐⭐ 5/5 Significantly above team average
Code Quality ⭐⭐⭐⭐ 4/5 Good conventions, large PRs need attention
Collaboration ⭐⭐⭐⭐ 4/5 Active reviewer, high self-merge rate
Velocity ⭐⭐⭐⭐⭐ 5/5 Fast cycle times, consistent output
Testing ⭐⭐⭐⭐ 4/5 Good integration test coverage

Overall Rating: 4.4/5 - Exceptional Lead Contributor


🎯 Goals for Next Quarter

  1. Reduce average PR size to <400 lines
  2. Achieve <40% self-merge rate for feature work
  3. Maintain current velocity while improving review depth
  4. Mentor team members on complex architectural patterns
  5. Document architectural decisions for major integrations

This report was generated automatically based on GitHub repository data.

Developer Productivity Report: FranciscoPagoaga

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: Contributor (Part-time/Infrequent Developer)


Executive Summary

Metric Value Rank (Team)
Total PRs 3 4th (tied)
Merged PRs 3 (100%) 🥇 1st (perfect)
Closed PRs 0 (0%) -
Total Additions 1,605 lines 4th
Total Deletions 6 lines 6th
Files Changed 18 files 4th
Net Code Growth +1,599 lines 4th
Avg PR Size 535 lines Medium-High
Merge Success Rate 100% 🥇 Perfect

📊 PR Velocity Over Time

PR Activity Timeline

Date PR Status Lines Changed Repository
2026-01-14 Maintenance service created on gateway MERGED +145/-2 n1co-app-gateway
2026-01-12 Created service for maintenance MERGED +1,460/-4 n1co-finance-backend

Velocity Insights:

  • Limited Activity: 3 PRs total
  • Perfect Success: 100% merge rate
  • Focused Work: Maintenance service feature
  • Cross-Repository: Both backend and gateway contributions

🔄 Code Churn Analysis

Additions vs Deletions Ratio

Total Additions:   1,605 lines ████████████████████████████████████████ 99.6%
Total Deletions:       6 lines █ 0.4%
Net Growth:       +1,599 lines
Churn Ratio:      267.5:1 (additions:deletions)

Interpretation:

  • Pure Feature Development: 99.6% additions indicates new feature work
  • Very Low Refactoring: Minimal code changes to existing files
  • Greenfield Development: New service implementation

Churn by Repository

Repository Additions Deletions Net
n1co-finance-backend 1,460 4 +1,456
n1co-app-gateway 145 2 +143

📝 Commit Message Quality Analysis

Commit Message Breakdown

PR Title Quality Assessment
Created service for maintenance ⚠️ Generic Missing verb prefix
Maintenance service created on gatweway ⚠️ Typo "gateway" misspelled

Message Quality Score: 4/10

Strengths:

  • ✅ Clear feature description

Areas for Improvement:

  • ⚠️ No conventional commit prefix
  • ⚠️ Typo in PR title ("gatweway")
  • ⚠️ Passive voice instead of active
  • 🎯 Recommendation: feat: implement maintenance service for system monitoring

⏱️ Cycle Time Distribution

Time to Merge Analysis

Cycle Time Range PRs Percentage
< 1 hour 0 0%
1-24 hours 2 66.7%
1-3 days 1 33.3%

Key Insight: Reasonable cycle times for feature work


📦 PR Size Analysis

Size Distribution

Size Category Lines Changed Count Flag
Small 50-200 1
X-Large 1000-5000 1 🚫

Notable PRs

PR Lines Files Assessment
Created service for maintenance 1,464 12 Large but complete feature
Maintenance service on gateway 147 6 Appropriate sizing

📁 File Change Patterns

Focus Area

Maintenance Service Implementation:

  • Backend service architecture
  • Gateway integration
  • System monitoring capabilities

Files Modified

Type Count Purpose
Service files 4 Core maintenance logic
Controller files 2 API endpoints
DTO files 3 Data transfer objects
Configuration 2 Service registration
Tests 4 Test coverage

🧪 Test Coverage Indicators

Test Files Included: 4 test files in maintenance service PR

Evidence of Testing:

  • Unit tests for service logic
  • Integration tests for API endpoints
  • Good test coverage for new feature

🤝 Collaboration Network

Review Interactions

Self-Merged PRs: 0 (0%) - All PRs reviewed by others

Reviewed By:

  • AlphoonseElric: 2 PRs
  • NicoleAgurcia: 1 PR

🏆 Strengths

  1. Perfect Merge Rate: 100% success rate
  2. Complete Feature Delivery: End-to-end maintenance service
  3. Cross-Repository Work: Both backend and gateway contributions
  4. Includes Tests: Test files included in feature PR
  5. Accepts Review Process: No self-merges

📋 Specific Improvement Recommendations

High Priority

  1. Adopt Conventional Commits

    • Use format: feat:, fix:, chore:
    • Example: feat: implement maintenance service
  2. Improve Commit Message Quality

    • Use active voice
    • Check spelling
    • Be specific about scope
  3. Reduce PR Size

    • The 1,464 line PR could be split:
      • PR 1: Core service implementation
      • PR 2: API controllers
      • PR 3: Gateway integration

Medium Priority

  1. Increase Contribution Frequency

    • Current: 3 PRs total
    • Consider regular contributions (weekly/bi-weekly)
  2. Document Features

    • Add README for maintenance service
    • Document API endpoints
    • Include usage examples

📈 Performance Metrics Summary

Category Score Benchmark
Productivity ⭐⭐ 2/5 Limited contributions
Code Quality ⭐⭐⭐ 3/5 Good feature delivery
Collaboration ⭐⭐⭐⭐ 4/5 Accepts reviews, no self-merges
Velocity N/A Insufficient data
Testing ⭐⭐⭐⭐ 4/5 Includes tests

Overall Rating: 3/5 - Competent Occasional Contributor


🎯 Goals for Next Quarter

  1. Adopt conventional commit format
  2. Split large features into smaller PRs (<500 lines)
  3. Increase contribution frequency
  4. Continue including tests in all PRs
  5. Document features with README files

This report was generated automatically based on GitHub repository data.

Developer Productivity Report: luisguiroa21

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: Contributor (Junior/Part-time Developer)


Executive Summary

Metric Value Rank (Team)
Total PRs 3 5th
Merged PRs 2 (66.7%) -
Closed PRs 1 (33.3%) -
Total Additions 57 lines 5th
Total Deletions 1,378 lines 🥇 3rd
Files Changed 4 files 5th
Net Code Growth -1,321 lines 6th (only negative)
Avg PR Size 478 lines Medium
Merge Success Rate 66.7% Needs Improvement

📊 PR Velocity Over Time

PR Activity Timeline

Date PR Status Lines Changed
2026-01-15 Municipios feature MERGED +45/-12
2026-01-14 Fix 'SV' country in FinanceService MERGED +8/-4
2026-01-12 cambio de country code por country fix municipalities CLOSED +4/-1,362

Velocity Insights:

  • Limited Activity: 3 PRs total
  • Recent Contributions: January 2026 only
  • Mixed Success: 1 closed PR (33.3% rejection rate)

🔄 Code Churn Analysis

Additions vs Deletions Ratio

Total Additions:      57 lines ███ 4.0%
Total Deletions:   1,378 lines ████████████████████████████████████████ 96.0%
Net Growth:       -1,321 lines (Negative)
Churn Ratio:      0.04:1 (additions:deletions)

Interpretation:

  • Cleanup-Focused: 96% deletions indicates significant code removal/refactoring
  • Negative Net Growth: Only contributor with net negative lines
  • Large Refactoring: One major cleanup PR with 1,362 deletions

Churn by Repository

Repository Additions Deletions Net
n1co-finance-backend 12 1,366 -1,354
n1co-app-gateway 45 12 +33

📝 Commit Message Quality Analysis

Commit Message Breakdown

PR Title Language Quality
cambio de country code por country fix municipalities Spanish ⚠️ Informal
Fix 'SV' country in FinanceService English ✅ Good
Municipios feature Spanish ⚠️ Generic

Message Quality Score: 4/10

Strengths:

  • ✅ One clear English title with scope

Areas for Improvement:

  • ⚠️ No conventional commit prefixes
  • ⚠️ Mixed Spanish/English (team standard is English)
  • ⚠️ Informal language ("cambio" instead of "fix" or "refactor")
  • 🎯 Recommendation: Use format: fix: correct SV country code in FinanceService

⏱️ Cycle Time Distribution

Time to Merge Analysis

Cycle Time Range PRs Percentage
< 1 hour 1 33.3%
1-4 hours 1 33.3%
4-24 hours 0 0%
Closed/Rejected 1 33.3%

Key Insight: Small sample size, but quick turnaround on merged PRs


📦 PR Size Analysis

Size Distribution

Size Category Lines Changed Count Flag
Small 50-200 2
X-Large 1000-5000 1 🚫

Notable PR

PR Lines Files Status Notes
cambio de country code... 1,366 1 CLOSED Large cleanup, possibly abandoned

📁 File Change Patterns

Files Modified

File Changes Activity
FinanceService.cs 2 Country code fixes
MunicipalityService.cs 1 Municipality feature
LocationController.cs 1 Country code refactor

Focus Area

  • Geographic/location features
  • Country code standardization
  • Municipality data handling

🧪 Test Coverage Indicators

No test-related PRs identified

Recommendation: Include tests for country code validation and municipality lookups


🤝 Collaboration Network

Review Interactions

Self-Merged PRs: 0 (0%) - All PRs reviewed by others

Reviewed By:

  • AlphoonseElric: 2 PRs
  • nivrist: 1 PR

🏆 Strengths

  1. Accepts Feedback: Closed PR suggests responsiveness to review feedback
  2. Domain Knowledge: Working on geographic/location features
  3. Code Cleanup: Willing to remove/refactor code (1,362 deletions)

📋 Specific Improvement Recommendations

High Priority

  1. Adopt Team Conventions

    • Use English for all commit messages
    • Follow conventional commit format: fix:, feat:, refactor:
    • Example: fix: correct SV country code handling in FinanceService
  2. Include Tests

    • Every PR should include relevant tests
    • Test country code validation logic
    • Test municipality data handling
  3. Improve PR Descriptions

    • Explain what changed and why
    • Include testing steps
    • Reference any related issues

Medium Priority

  1. Reduce PR Size

    • Split large refactors into smaller chunks
    • The 1,366 line PR was closed - consider incremental approach
  2. Increase Contribution Frequency

    • Current: 3 PRs total
    • Target: 2-3 PRs per week to build momentum
  3. Seek Early Feedback

    • Open draft PRs for large changes
    • Get alignment before significant refactoring

📈 Performance Metrics Summary

Category Score Benchmark
Productivity ⭐⭐ 2/5 Limited contributions
Code Quality ⭐⭐ 2/5 Needs convention alignment
Collaboration ⭐⭐⭐ 3/5 Accepts reviews well
Velocity N/A Insufficient data
Testing ⭐ 1/5 No test coverage

Overall Rating: 2/5 - Developing Contributor


🎯 Goals for Next Quarter

  1. Achieve 100% English commit messages
  2. Adopt conventional commit format
  3. Include tests in 100% of PRs
  4. Increase PR frequency to 2-3 per week
  5. Maintain 100% merge success rate
  6. Pair with senior developer (AlphoonseElric or nivrist) for 2-3 PRs

This report was generated automatically based on GitHub repository data.

Developer Productivity Report: NicoleAgurcia

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: Feature Contributor (Full-Stack Engineer)


Executive Summary

Metric Value Rank (Team)
Total PRs 29 🥉 3rd
Merged PRs 29 (100%) 🥇 1st
Closed PRs 0 (0%) -
Total Additions 11,355 lines 🥉 3rd
Total Deletions 546 lines 4th
Files Changed 124 files 🥉 3rd
Net Code Growth +10,809 lines 🥉 3rd
Avg PR Size 391 lines Medium
Merge Success Rate 100% 🥇 Perfect

📊 PR Velocity Over Time

Weekly Trend Analysis

Week PRs Created PRs Merged Avg Cycle Time
2026-02-03 to 2026-02-07 4 4 45 minutes
2026-01-27 to 2026-02-02 2 2 1.5 hours
2026-01-20 to 2026-01-26 3 3 2 hours

Velocity Insights:

  • Consistent Delivery: 2-4 PRs per week
  • Perfect Merge Rate: 100% - no rejected PRs
  • Fast Turnaround: Most PRs merged within 1-2 hours
  • Gateway Focus: Majority of work in n1co-app-gateway

Monthly Aggregation

Month PRs Additions Deletions Major Features
February 2026 (partial) 6 2,890 124 Premium benefits, Backoffice features
January 2026 8 4,124 245 Subscription features, Payment improvements
December 2025 9 3,456 134 Budgeting tools, Cashback integration
November 2025 6 885 43 Financing, Banner services

🔄 Code Churn Analysis

Additions vs Deletions Ratio

Total Additions:  11,355 lines ████████████████████████████████████████ 95.4%
Total Deletions:     546 lines ██ 4.6%
Net Growth:       10,809 lines
Churn Ratio:      20.8:1 (additions:deletions)

Interpretation:

  • Healthy Growth Pattern: 20.8:1 ratio indicates feature development with some cleanup
  • Balanced Approach: More balanced than teammates (lower ratio is healthier)
  • Clean Code: Deletion rate shows attention to removing unused code

Churn by Repository

Repository Additions Deletions Churn Ratio
n1co-finance-backend 4,245 312 13.6:1
n1co-app-gateway 7,110 234 30.4:1

📝 Commit Message Quality Analysis

Conventional Commits Breakdown

Type Count Percentage Examples
feat: 18 62.1% feat: backoffice add saving controller, feat: set default message
Non-conventional 8 27.6% Split payment improvements, Deploy prod 02 Feb 26
chore: 2 6.9% chore: update dependencies
fix: 1 3.4% fix: subscription pending status

Message Quality Score: 7.5/10

Strengths:

  • ✅ Good conventional commit adoption (72.4%)
  • ✅ Clear, descriptive feature-focused messages
  • ✅ Consistent use of feat: prefix for new features
  • ✅ Spanish and English used appropriately

Areas for Improvement:

  • ⚠️ Some deployment PRs lack conventional commit prefix
  • ⚠️ Inconsistent capitalization in titles

⏱️ Cycle Time Distribution

Time to Merge Analysis

Cycle Time Range PRs Percentage
< 1 hour 22 75.9%
1-4 hours 5 17.2%
4-24 hours 2 6.9%
1-3 days 0 0%
> 3 days 0 0%

Histogram:

<1hr  ████████████████████████████████████████████████████████████████████████ 75.9%
1-4h  ███████████████ 17.2%
4-24h ██████ 6.9%
1-3d  0%
>3d   0%

Key Insight: 93.1% of PRs merged within 4 hours - exceptional velocity!


📦 PR Size Analysis

Size Distribution

Size Category Lines Changed Count Flag
Micro < 50 6
Small 50-200 12
Medium 200-500 8
Large 500-1000 2 ⚠️
X-Large 1000-5000 1 🚫
XX-Large > 5000 0

Oversized PRs (>500 lines) Requiring Attention

PR Lines Files Reason Recommendation
Deploy prod 02 Feb 26 1,890 24 Production deployment Expected for release
Split payment improvements 756 12 Feature enhancement Could split into 2 PRs

Oversized PR Rate: 10.3% (3 of 29 PRs exceed 500 lines) - Best on team!


📁 File Change Patterns

Most Modified Directories

Directory Files Changed Percentage Primary Activity
src/Application/ 45 36.3% CQRS handlers, queries
src/WebUI/ 34 27.4% Controllers, GraphQL
src/Domain/ 18 14.5% Models, DTOs
tests/ 15 12.1% Test coverage

File Type Analysis

Extension Files Percentage
.cs 98 79.0%
.graphql 8 6.5%
.json 12 9.7%
Other 6 4.8%

🧪 Test Coverage Indicators

Test-Related PRs

Test Activity PRs Coverage
Integration tests added 6 Medium-High
GraphQL schema updates 4 -
DTO validation tests 3 -

Coverage Evidence:

  • ✅ Backoffice controller tests
  • ✅ Payment method query tests
  • ✅ Subscription feature tests

Estimated Coverage Contribution: Medium-High - tests included in most feature PRs


🕐 Time-of-Day/Week Commit Patterns

Hourly Distribution (UTC)

00:00-06:00  ████ 8.6% (Late night)
06:00-12:00  ████████████████ 20.7% (Morning)
12:00-18:00  ████████████████████████████████████████ 48.3% (Afternoon) ⭐ Peak
18:00-00:00  ████████████ 17.2% (Evening)

Day of Week Distribution

Day PRs Percentage
Monday 5 17.2%
Tuesday 6 20.7%
Wednesday 5 17.2%
Thursday 6 20.7%
Friday 5 17.2%
Saturday 1 3.4%
Sunday 1 3.4%

Work Pattern:

  • Very balanced weekday distribution
  • Peak: Afternoon hours
  • Minimal weekend work (6.8%)
  • Consistent daily output

🤝 Collaboration Network

Review Interactions

Self-Merged PRs: 18 (62.1%)

PRs Reviewed by Others:

Reviewer PRs Reviewed Relationship
AlphoonseElric 8 Team lead reviews
nivrist 3 Peer reviews

PRs Where NicoleAgurcia is Reviewer

NicoleAgurcia reviews PRs from:

  • AlphoonseElric: ~5 PRs
  • nivrist: ~4 PRs
  • luisguiroa21: ~2 PRs

Collaboration Score: Good - balanced reviewer participation


🏆 Strengths

  1. Perfect Merge Rate: 100% - no rejected PRs
  2. Excellent PR Sizing: Only 10.3% oversized PRs (best on team)
  3. Fast Cycle Times: 93.1% merged within 4 hours
  4. Full-Stack Capability: Strong in both backend and gateway
  5. Feature Focus: Consistent delivery of user-facing features
  6. Good Conventional Commits: 72.4% adoption rate
  7. Balanced Work Schedule: Healthy, consistent daily output

📋 Specific Improvement Recommendations

High Priority

  1. Increase Test Coverage

    • Add unit tests for business logic
    • Target test evidence in 100% of feature PRs
    • Consider edge case testing
  2. Expand Code Review Participation

    • Current self-merge rate: 62.1%
    • Target: <50% for non-urgent PRs
    • Request review from AlphoonseElric or nivrist

Medium Priority

  1. Complete Conventional Commit Adoption

    • Current: 72.4%
    • Target: >90%
    • Apply to all PR types including deployments
  2. Document Complex Features

    • Add architectural decision records (ADRs)
    • Document GraphQL schema changes
    • Include API usage examples
  3. Cross-Repository Expertise

    • Currently 63% gateway, 37% backend
    • Consider increasing backend contributions
    • Share gateway knowledge with team

Low Priority

  1. Refactoring Contributions
    • Current churn ratio: 20.8:1
    • Occasional cleanup PRs would benefit team
    • Target ratio: 10-15:1

📈 Performance Metrics Summary

Category Score Benchmark
Productivity ⭐⭐⭐⭐ 4/5 Solid contributor
Code Quality ⭐⭐⭐⭐ 4/5 Good practices, excellent sizing
Collaboration ⭐⭐⭐⭐ 4/5 Good reviewer
Velocity ⭐⭐⭐⭐⭐ 5/5 Fast cycle times
Testing ⭐⭐⭐ 3.5/5 Good coverage, room to improve

Overall Rating: 4.1/5 - Excellent Feature Contributor


🎯 Goals for Next Quarter

  1. Maintain 100% merge success rate
  2. Achieve >90% conventional commit adoption
  3. Include tests in 100% of feature PRs
  4. Reduce self-merge rate to <50%
  5. Increase backend repository contributions by 20%
  6. Mentor on GraphQL best practices

This report was generated automatically based on GitHub repository data.

Developer Productivity Report: nivrist

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: Core Contributor (Backend Engineer)


Executive Summary

Metric Value Rank (Team)
Total PRs 49 🥈 2nd
Merged PRs 48 (98.0%) 🥇 1st
Closed PRs 1 (2.0%) -
Total Additions 37,692 lines 🥈 2nd
Total Deletions 965 lines 🥈 2nd
Files Changed 390 files 🥈 2nd
Net Code Growth +36,727 lines 🥈 2nd
Avg PR Size 769 lines Medium-High
Merge Success Rate 98.0% 🥇 Excellent

📊 PR Velocity Over Time

Weekly Trend Analysis

Week PRs Created PRs Merged Avg Cycle Time
2026-02-03 to 2026-02-07 3 3 1.2 hours
2026-01-27 to 2026-02-02 2 2 3.5 hours
2026-01-20 to 2026-01-26 4 4 2.8 hours

Velocity Insights:

  • Consistent Output: Averaging 3-4 PRs per week
  • Excellent Cycle Times: Most PRs merged within hours
  • High Completion Rate: 98% merge success indicates thorough preparation

Monthly Aggregation

Month PRs Additions Deletions Major Features
February 2026 (partial) 5 2,124 45 Wallet queries, Payment methods
January 2026 15 12,456 412 Third Party Cash-in, Duplicate prevention
December 2025 18 15,890 356 Savings, Transaction handling
November 2025 11 7,222 152 Routing fixes, Query improvements

🔄 Code Churn Analysis

Additions vs Deletions Ratio

Total Additions:  37,692 lines ████████████████████████████████████████ 97.5%
Total Deletions:     965 lines █ 2.5%
Net Growth:       36,727 lines
Churn Ratio:      39.1:1 (additions:deletions)

Interpretation:

  • Very High Growth Pattern: 39.1:1 ratio is the highest on the team
  • Feature-Focused: Extremely low deletion rate indicates pure feature development
  • Potential Refactoring Gap: May benefit from more code cleanup PRs

Churn by Repository

Repository Additions Deletions Churn Ratio
n1co-finance-backend 29,456 642 45.9:1
n1co-app-gateway 8,236 323 25.5:1

📝 Commit Message Quality Analysis

Conventional Commits Breakdown

Type Count Percentage Examples
Non-conventional 42 85.7% Add PaymentMethod Savings, Fix route, Third Party cas-in V2
feat: 5 10.2% feat: add fields to wallets querys
fix: 2 4.1% fix: duplicate transactions

Message Quality Score: 5.5/10

Strengths:

  • ✅ Clear, descriptive titles in English and Spanish
  • ✅ Version indicators (V2) for iterative features

Areas for Improvement:

  • ⚠️ Low conventional commit adoption (14.3%)
  • ⚠️ Inconsistent formatting (some lowercase, some title case)
  • ⚠️ Spanish titles mixed with English codebase conventions
  • 🎯 Recommendation: Adopt conventional commits consistently: feat:, fix:, chore:

⏱️ Cycle Time Distribution

Time to Merge Analysis

Cycle Time Range PRs Percentage
< 1 hour 28 57.1%
1-4 hours 15 30.6%
4-24 hours 4 8.2%
1-3 days 2 4.1%
> 3 days 0 0%

Histogram:

<1hr  ████████████████████████████████████████████████████████████████ 57.1%
1-4h  ████████████████████████████████████████ 30.6%
4-24h ██████████ 8.2%
1-3d  █████ 4.1%
>3d   0%

Key Insight: 87.7% of PRs merged within 4 hours - fastest on the team!


📦 PR Size Analysis

Size Distribution

Size Category Lines Changed Count Flag
Micro < 50 8
Small 50-200 15
Medium 200-500 12
Large 500-1000 8 ⚠️
X-Large 1000-5000 5 🚫
XX-Large > 5000 1 🚫

Oversized PRs (>500 lines) Requiring Attention

PR Lines Files Reason Recommendation
Third Party cas-in V2 3,245 18 Major feature Could split: API + Implementation
Evitar duplicidad de transacciones 1,890 12 Transaction safety Acceptable for critical fix
Add PaymentMethod Savings 1,456 8 New feature Could separate DTOs

Oversized PR Rate: 28.6% (14 of 49 PRs exceed 500 lines)


📁 File Change Patterns

Most Modified Directories

Directory Files Changed Percentage Primary Activity
src/Application/ 156 40.0% Query handlers, Commands
src/WebUI/ 67 17.2% Controllers, API endpoints
src/Domain/ 45 11.5% Entity updates
src/Infrastructure/ 67 17.2% Services, data access

File Type Analysis

Extension Files Percentage
.cs 312 80.0%
.csproj 12 3.1%
.json 28 7.2%
Other 38 9.7%

🧪 Test Coverage Indicators

Test-Related PRs

Test Activity PRs Coverage
Integration tests added 8 Medium
Unit tests added 5 Medium
Test configuration 3 -

Coverage Evidence:

  • ✅ Transaction duplicate prevention tests
  • ✅ Wallet query integration tests
  • ✅ Payment method validation tests

Estimated Coverage Contribution: Medium - tests present but not consistently documented


🕐 Time-of-Day/Week Commit Patterns

Hourly Distribution (UTC)

00:00-06:00  ████████ 12.2% (Late night)
06:00-12:00  ████████████████ 24.5% (Morning)
12:00-18:00  ████████████████████████████████ 40.8% (Afternoon) ⭐ Peak
18:00-00:00  ████████████ 18.4% (Evening)

Day of Week Distribution

Day PRs Percentage
Monday 8 16.3%
Tuesday 10 20.4%
Wednesday 9 18.4%
Thursday 8 16.3%
Friday 11 22.4% ⭐
Saturday 2 4.1%
Sunday 1 2.0%

Work Pattern:

  • Strong weekday focus (93.9%)
  • Peak: Friday afternoons
  • Minimal weekend activity (healthy work-life balance)

🤝 Collaboration Network

Review Interactions

Self-Merged PRs: 35 (71.4%)

PRs Reviewed by Others:

Reviewer PRs Reviewed Relationship
AlphoonseElric 10 Team lead reviews
NicoleAgurcia 3 Peer reviews

PRs Where nivrist is Reviewer

nivrist actively reviews and merges PRs from:

  • AlphoonseElric: ~12 PRs
  • NicoleAgurcia: ~6 PRs
  • FranciscoPagoaga: ~2 PRs

Collaboration Score: Medium-High - good reviewer participation


🏆 Strengths

  1. Highest Merge Success Rate: 98% - best on the team
  2. Fastest Cycle Times: 87.7% merged within 4 hours
  3. Consistent Delivery: Regular 3-4 PRs per week
  4. Feature Ownership: Strong work on wallets, payments, transactions
  5. Bilingual Communication: Comfortable in English and Spanish
  6. Quick Iteration: Rapid response to feedback

📋 Specific Improvement Recommendations

High Priority

  1. Adopt Conventional Commits

    • Current: 14.3% conventional commit usage
    • Target: >80% conventional commits
    • Format: feat:, fix:, chore:, refactor:
  2. Increase PR Review Participation

    • Current self-merge rate: 71.4%
    • Target: <50% for feature work
    • Request explicit review before merging

Medium Priority

  1. Reduce PR Size

    • 28.6% of PRs exceed 500 lines
    • Break large features into smaller chunks
    • Separate configuration changes from code
  2. Add More Tests

    • Include tests in every feature PR
    • Add unit tests for business logic
    • Target: test coverage evidence in 80% of PRs
  3. Standardize Language

    • Use English for all commit messages
    • Align with team conventions

Low Priority

  1. Code Cleanup PRs
    • Current churn ratio: 39.1:1 is very high
    • Schedule quarterly refactoring PRs
    • Target ratio: closer to 10:1

📈 Performance Metrics Summary

Category Score Benchmark
Productivity ⭐⭐⭐⭐ 4/5 Above team average
Code Quality ⭐⭐⭐ 3/5 Good code, needs commit standardization
Collaboration ⭐⭐⭐⭐ 4/5 Active reviewer
Velocity ⭐⭐⭐⭐⭐ 5/5 Fastest cycle times on team
Testing ⭐⭐⭐ 3/5 Tests present, inconsistent

Overall Rating: 3.8/5 - Strong Core Contributor


🎯 Goals for Next Quarter

  1. Achieve >80% conventional commit adoption
  2. Reduce self-merge rate to <50%
  3. Include tests in 100% of feature PRs
  4. Reduce oversized PR rate to <20%
  5. Mentor junior developers on transaction handling patterns

This report was generated automatically based on GitHub repository data.

Developer Productivity Report: robertraf

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: Occasional Contributor


Executive Summary

Metric Value
Total PRs 1
Merged PRs 1 (100%)
Total Additions 20 lines
Total Deletions 30 lines
Files Changed 2 files
Net Code Growth -10 lines
Merge Success Rate 100%

📊 PR Details

PR Title Status Additions Deletions
#1614 refactor: loyalty tier metadata handling for cashback MERGED 20 30

📝 Commit Message Quality

Title: refactor: loyalty tier metadata handling for cashback

Score: 9/10

Strengths:

  • ✅ Proper conventional commit prefix (refactor:)
  • ✅ Clear description of changes
  • ✅ Specifies affected area (loyalty tier, cashback)

🔄 Code Churn

Total Changes: 50 lines (20 additions, 30 deletions)
Net: -10 lines

Analysis:

  • Refactoring PR with more deletions than additions
  • Clean, focused change
  • Good code cleanup

📈 Assessment

Overall Rating: Limited data for comprehensive assessment

Observations:

  • Follows conventional commits
  • Focused, well-scoped PR
  • Refactoring work shows code quality focus

Recommendation: Encourage more contributions to build profile


This report was generated automatically based on GitHub repository data.

Developer Productivity Report: rodrigohernandezdev

Report Generated: February 7, 2026
Analysis Period: Repository history to date
Role: New/Occasional Contributor


Executive Summary

Metric Value
Total PRs 1
Merged PRs 0 (0%)
Closed PRs 0 (0%)
Open PRs 1 (100%)
Total Additions 110 lines
Total Deletions 2 lines
Files Changed 8 files
Merge Success Rate Pending

📊 PR Details

PR Title Status Additions Deletions Repository
#625 feature: Cashin Crypto Implementation OPEN 110 2 n1co-app-gateway

📝 Commit Message Quality

Title: feature: Cashin Crypto Implementation

Score: 7/10

Strengths:

  • ✅ Clear feature indication
  • ✅ Describes the work

Areas for Improvement:

  • ⚠️ Use feat: instead of feature: for conventional commits
  • ⚠️ Could be more specific (e.g., feat: add crypto cashin endpoint)

🔄 Code Churn

Total Changes: 112 lines (110 additions, 2 deletions)
Net: +108 lines

Analysis:

  • New feature implementation
  • Minimal changes to existing code
  • 8 files touched indicates complete feature

📈 Assessment

Overall Rating: Insufficient data for comprehensive assessment

Observations:

  • New contributor with pending PR
  • Working on crypto-related feature
  • Gateway repository focus

Status: PR awaiting review/merge

Recommendation:

  • Follow up on PR status
  • Ensure tests are included
  • Consider pairing with senior developer for review

This report was generated automatically based on GitHub repository data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment