issue-card-writer

Context: The WeBuddhist team (backend, frontend, app devs) uses GitHub issue cards to document API endpoints during integration. Cards must be consistent so any dev can scan them and know: what's the endpoint, what goes in, what comes out, and what can go wrong. This skill generates those cards.

Accepted Inputs:

• OpenAPI/Swagger spec (YAML/JSON) → extract endpoints automatically
• Natural language → "we added a language filter to GET /plans/tags"
• Inline details → method, path, params, response pasted in chat
• Existing issue number → reads via gh issue view for context
• Any combination of the above

Instructions:

1. Parse the input. Extract: HTTP method, path, query params, request body, response body, status codes, headers. If info is missing, mark as [TBD].

2. Pick the card type:

   • New endpoint → full card
   • Endpoint edit → full card + "Current Behavior" / "Proposed Change" sections after Context
   • Backend fix → full card, focus Context on the bug, still include the related endpoint and response so devs know which API surface is affected