Analyze git diffs to identify required documentation updates after code changes.
npx skills add https://github.com/LukasStrickler/ai-dev-atelier --skill docs-check
Please help me install this Agent Skill. Skill: docs-check Source: https://github.com/LukasStrickler/ai-dev-atelier/tree/main/content/skills/docs-check Command: npx skills add https://github.com/LukasStrickler/ai-dev-atelier --skill docs-check
This Skill analyzes git diffs to surface documentation gaps and recommends files to review, keeping docs synchronized with code changes.
Run the documentation check with:
High-intent search queries and answers about installing and using this skill.
To identify required documentation updates after code changes, analyze your git diff to surface gaps across API, database, and component modifications, then review the suggested documentation files to ensure docs stay synchronized with the codebase.
The best way to keep documentation aligned before committing is to run a pre-commit check that scopes git diff changes across API, database, and configuration categories, then references your repository's Documentation Guide to recommend relevant files for review.
Analyzing a git diff identifies required documentation updates by categorizing code changes across API, database, components, configuration, and authentication scopes, then suggesting relevant documentation files to review for alignment with repository standards.
Yes, you can use a documentation check to scope changes across API and database modifications by analyzing your git diff to categorize code changes and suggest relevant documentation files to review for each affected scope.
Yes, you need a Documentation Guide in your repository to enforce documentation alignment, as the check references this guide and related docs to direct updates and ensure code changes stay synchronized with repository standards.
The best way to find documentation gaps after modifying configuration files is to run a documentation check that analyzes your git diff, categorizes the configuration changes, and suggests relevant documentation files to review for necessary updates.
binoy14Generate Conventional Commits messages from staged git diffs.
tnezInstall a Git pre-commit hook that lints staged Markdown files with markdownlint-cli2.
kissrosecicd-hubScan Git diffs for exposed credentials using entropy analysis and regex patterns.
saschadudkin-sketchAutomate code review for rezidence4/DomHub repository changes.
