JGit documentation and API reference with code examples
92
Pending
Does it follow best practices?
Impact
92%
1.09xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "Tests whether the agent implements robust Git synchronization with retry logic, error handling patterns, and resilience strategies for network operations.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Retry logic implementation",
"description": "Implements retry logic with exponential backoff for network operations",
"max_score": 10
},
{
"name": "TransportException handling",
"description": "Specifically handles TransportException for network-related Git failures",
"max_score": 10
},
{
"name": "Error handler pattern",
"description": "Uses separated error handler interfaces or classes for different error types",
"max_score": 10
},
{
"name": "Circuit breaker pattern",
"description": "Implements circuit breaker to prevent overwhelming remote servers during outages",
"max_score": 10
},
{
"name": "Configurable retry parameters",
"description": "Makes retry behavior configurable (max attempts, backoff multiplier, retryable exceptions)",
"max_score": 10
},
{
"name": "Resource cleanup",
"description": "Ensures Git and Repository resources are properly cleaned up even during retry loops",
"max_score": 10
},
{
"name": "Status reporting",
"description": "Provides detailed status reporting for operations (success, failure after retries, errors)",
"max_score": 10
},
{
"name": "Thread safety",
"description": "Design considers thread safety for concurrent operations (or documents limitations)",
"max_score": 10
},
{
"name": "Authentication handling",
"description": "Handles authentication failures gracefully with appropriate error messages",
"max_score": 10
},
{
"name": "Test coverage",
"description": "Includes unit tests demonstrating retry behavior with mocked network failures",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5