leap-year-analyzer

A Gregorian leap year is divisible by 4, except for years divisible by 100 (which are not leap years) unless also divisible by 400. For example, 2000 is a leap year, but 1900 is not. This Skill applies these rules to validate years between 1582–9999.

The Julian calendar treats any year divisible by 4 as a leap year, without the 100/400 exceptions used in the Gregorian system. This Skill compares both systems so you can see how the same year behaves under each calendar standard.

Yes, this Skill determines leap-year status for Gregorian, Julian, Hebrew, and Chinese calendars, applying each system's specific intercalation rules. You can validate a single year or perform batch checks across all four calendar systems within the supported range.

Year 2100 is divisible by 100 but not by 400, making it a common year in the Gregorian calendar but a leap year in the Julian system. This Skill explains such rule differences and helps debug calendar conversion edge cases.

The Skill validates years from 1582 to 9999 for the Gregorian calendar, with specific range checks applied to Julian, Hebrew, and Chinese calendars. Attempting to analyze years outside these ranges will return a validation error.

Yes, the Skill exports an `isLeapYear(year, calendar)` function and an API route for batch leap-year validation. You can integrate it to enforce year-range constraints (1582–9999) and apply calendar-specific leap-year logic in production workflows.