sisters

What problem does it solve?

It prevents hidden inconsistencies across related repositories (the “sisters”) by auditing CI/action pins, toolchain settings, merge policies, and repo hygiene so you don’t discover drift the hard way during releases or onboarding.

Core Features & Use Cases

• Action-pin drift detection: Compares uses: owner/action@version pins across sisters and reports mismatched versions that can cause flaky CI or divergent behaviors.
• Skill-context structural parity: Verifies required .claude/skill-context.md sections exist consistently across sisters to avoid missing operational scaffolding.
• GitHub merge-setting drift and protection checks: Detects divergence in merge rules and validates that main is protected with required checks and safe settings.
• Toolchain pin drift in pyproject.toml: Surfaces drift in requires-python, Ruff target-version, and dev tool specs (ruff, ty, pytest) at the root pyproject.toml level.
• Operational hygiene signals: Rolls up open PRs, flags stale branches, checks local main vs origin/main divergence, and looks for conventions like Codecov config and log-retention policies.

Quick Start

Run the Sisters audit by asking the AI to invoke techne:sisters and then paste the output report back for review.