web-check

Verify branch code changes against official documentation and API best practices.

Updated Sep 9, 2024
One-click install
npx skills add https://github.com/axel-kaliff/dotfiles --skill web-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-check
Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/web-check
Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill web-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Search the web and official documentation to verify that branch changes follow best practices, use APIs correctly, and don't reinvent existing solutions.

Core Features & Use Cases

  • Web-guided verification of code changes against official docs and best practices.
  • API usage validation, deprecations checks, and correctness of library calls.
  • Guidance for merge reviews with actionable recommendations based on findings.

Quick Start

Run web-check on the current branch to verify branch changes against best practices and official documentation.

Frequently Asked Questions about web-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify branch changes against best practices and official documentation?

You verify branch changes by searching official documentation to validate API usage, check for deprecations, and confirm correct library patterns. This process reviews changed files to ensure they follow best practices and avoid reinventing existing solutions.

What is web-guided code review for API usage validation?

Web-guided code review is a verification method that searches official documentation to validate API calls, detect deprecated library usage, and provide best-practice recommendations for changed files in a branch.

How do I check code changes for deprecated APIs before merge?

To check code changes for deprecated APIs, apply web-guided verification to the changed files in your branch. This validates API calls against official documentation and generates a concise report with deprecation warnings and source links.

Can I use automated documentation checks for merge reviews?

Yes, you can use automated documentation checks to guide merge reviews. This process validates branch changes against official docs, providing actionable recommendations based on findings to ensure correct API usage and library patterns.

What's the best way to validate library calls in a feature branch?

The best way to validate library calls is to verify branch changes against official documentation. This targets non-trivial transformations and library patterns, ensuring correct API usage while avoiding reinventing existing solutions.