skills.rest
wolfbela
wolfbelaCOMMUNITY
Explore all skills by this author →
GitHub

front-doc

Generate frontend API documentation from GitHub PRs.

Updated Aug 27, 2026
Search Tags:#documentation#frontend#github#endpoints#pull-requests#api-changes
One-click install
npx skills add https://github.com/wolfbela/claude-skill --skill front-doc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: front-doc
Source: https://github.com/wolfbela/claude-skill/tree/main/weshake/skills/front-doc
Command: npx skills add https://github.com/wolfbela/claude-skill --skill front-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Cette Skill génère une documentation frontend à partir d'une ou plusieurs PRs GitHub en analysant les changements d'API (endpoints, modèles, réponses) et produit un document clair pour l'équipe front.

## Core Features & Use Cases

  • Analyse les métadonnées des PR pour identifier les changements côté front (endpoints, schémas de réponse, nouveaux champs).
  • Produit un document consolidé et lisible pour l'équipe front, prêt à être partagé.
  • Cas d'utilisation : lorsque plusieurs PR modifient l'API frontend, générer automatiquement un document unique mettant en évidence les changements et leurs impacts sur l'UI.

### Quick Start Fournissez une liste de numéros de PR et laissez l'outil générer automatiquement la documentation front-end.

Frequently Asked Questions about front-doc

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

FAQPage Schema
How do I generate frontend API documentation from GitHub pull requests?▼

To generate frontend API documentation from GitHub pull requests, provide a list of PR numbers to the tool. It analyzes API changes across endpoints, models, and responses, producing a consolidated document highlighting UI impacts ready for product and design teams.

What is the best way to document API changes for frontend teams when multiple PRs modify endpoints?▼

Documenting API changes for frontend teams from multiple PRs is best handled by consolidating the metadata into a single readable document. This process identifies new response fields and schema shifts, ensuring the frontend contracts are clearly communicated to product and design teams.

Can I automatically extract frontend contract changes from GitHub PRs?▼

Yes, you can automatically extract frontend contract changes from GitHub PRs. By analyzing pull request metadata, the tool identifies modifications to endpoints and response schemas, generating a clear document that outlines specific impacts on the user interface.

How do I consolidate API endpoint and model changes from several PRs into a single readable document?▼

You can consolidate API endpoint and model changes from several PRs by supplying the PR numbers to this documentation generator. It parses changes and outputs a single, readable frontend document ready to be distributed to your product and design teams.

Does this frontend documentation generator work for projects with frequent API changes across multiple endpoints?▼

Yes, this frontend documentation generator is specifically designed for projects with frequent API changes across multiple endpoints. It processes multiple pull requests simultaneously to ensure all frontend contract modifications are captured and summarized for the frontend team.

Related Skills

Explore More Software Engineering Skills→
navidemadnavidemad

publish

Generate conventional commit messages and GitHub pull request descriptions.

Community
Intermediate
dankoflydankofly

full-stack

Coordinate backend and frontend changes for end-to-end features.

Community
Advanced
791994545791994545
4

github-ops

Manage GitHub pull requests, issues, repositories, workflows, and API endpoints via gh CLI.

Community
Advanced
KentoShimizuKentoShimizu
7

documentation-api-reference

Generate contract-aligned API reference documentation with endpoints, schemas, and error codes.

Community
Advanced