kin
Tracks AI-generated code changes and their dependencies before merge, reducing integration risk and enabling teams to understand impact across systems when A…
The system of record for AI-written software. A persistent graph of entities, relationships, changes, and provenance, so humans and AI agents see what a change touches before it merges. Beside Git today.
- Track which files and components an AI-generated code change impacts before merging
- Audit the provenance and relationships of AI-written code modifications across your codebase
- Review entity dependencies affected by AI suggestions to prevent unintended side effects
Tracks AI-generated code changes and their dependencies before merge, reducing integration risk and enabling teams to understand impact across systems when AI contributes to production codebases.
Engineering teams integrating AI coding assistants into CI/CD pipelines who need visibility into generated code dependencies.
https://github.com/firelock-ai/kin
By firelock-ai
How to Get It
claude plugins install firelock-ai/kin
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me track which files and components an AI-generated code change impacts before merging
Trust Signals Auto-scanned
Community Pulse Emerging
Discussed on Hacker News
- Show HN: Kin – A code repository built for AI and the people working with it — Hacker News · 3 pts
1 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 47 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 47 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.