garrytan / garrytan/gstack

Keep generated QA/deploy docs from erasing operational regression notes

Open
#1,708 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
133k
Forks
19.9k
Avg merge
18h 46m
Merged PRs (30d)
26

Description

## Problem

Some useful QA/deploy operational notes live in generated skill docs, but generation/upgrades can erase them unless the template/source path is updated too. Downstream patches currently preserve notes around QA regression resume, mobile auth/Clerk QA, Vercel deployment verification, and resolver utility hints.

## Expected behavior

Operationally useful guidance should live in the template/source files or a stable references directory so regeneration preserves it.

## Current downstream patch

Downstream commits patch both generated `SKILL.md` files and some `.tmpl` files, but this remains easy to regress when new docs are generated.

## Proposed direction

- Move recurring operational notes into stable `references/` files.
- Ensure generated `SKILL.md` files link to those references.
- Add a docs-generation check that prevents template/source drift from silently dropping operational references.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.