refactor(skills): draft ReadMe workflow-focused skill skeletons

[xavierandueza]

🚥 Resolves N/A

NOTE - ONLY LOOK AT the managing-readme-docs REST WILL BE UPDATED IN OTHER PRs.

🧰 Changes

This is a skeleton that I made for the Skills that we'll want moving forward. Other PRs merge into here, and once we're ready to go we merge this.

Note - it's intentionally minimalist at the moment so that we can continue to improve on this as we merge PRs that and we test to make sure that the skills work in actual onboarding workflows that we do.

🧬 QA & Testing

N/A - staging PR that others merge into.

[greptile-apps]

Confidence Score: 4/5

[Low impact] Reorganizes skill documentation and configuration files.

Confirm that a repository is connected through BiDi Sync before merging; otherwise requested hosted edits can remain local.

Findings

1.  Hosted docs stay unchanged ▶

_{Reviews (5) · Last reviewed commit: "chore: sync generated skills" · Reviewed by Greptile}

[xavierandueza]

(agent response)
Both findings are addressed: standalone project/API routing and connection verification before seeding. Local skill sync, frontmatter/size, whitespace, and local-reference checks passed. On this head, validate is successful and Greptile Review is in progress; the previous 3/5 confidence result was for the old head, so a fresh review is needed.

[xavierandueza]

(agent response)
Validate job 110748856324 fails at node scripts/sync-skills.mjs --check: 51 mirror mismatches, exit 1, reproduced locally on c1fae3d.

This is intentional staging: this PR changes only skills/; mirrored copies and CI remain untouched per the requested scope. Independent canonical-only validation passes for all six skills; later CI steps were skipped, not passed. No product changes or CI rerun: CI remains red until mirrors are synced at go-live or owners separately change the sync policy.

[xavierandueza]

(agent response)
Greptile completed successfully, but its check remains red: 4/5 is below the required 5/5. The latest summary cites client-copy synchronization and carries the old, already-replied/outdated local-seeding finding. On c1fae3d, canonical setup steps 4–6 route first and explicitly skip MCP for confirmed local-only work; no new canonical finding was posted.

No product changes: this draft intentionally stages only skills/; mirrors stay unchanged until go-live. Independent canonical validation passes all six skills. Neither CI nor the confidence gate is green; no rerun, threshold change, or thread-resolution action was taken.

[xavierandueza]

This is the ONLY one that has work in it this PR - IGNORE THE REST.

[greptile-apps]

Hosted docs stay unchanged

If the agent is in a repository containing docs/ or reference/ that has never been connected to ReadMe, this instruction still chooses Git for a request to update the hosted docs. The edits stay local, and the requested site remains unchanged.

Confirm that BiDi Sync connects this repository and its branch to the intended project before choosing local edits; otherwise use MCP. The same instruction appears at line 46 and in the Claude, Codex, and Cursor copies.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!