Repository navigation
Conversation
A created repo should not ship a README about being a template, so the file is now the skeleton that new repos start from: what the repo is, a Getting started section linking the contributing site, a Structure map for monorepos, and Related repositories. Commenting decisions were made based on what is true of an initialized repository. Git hooks remain rendered, but instructions on updating linters do not
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR rewrites |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
withinfocus
left a comment
withinfocus
left a comment
There was a problem hiding this comment.
You have a bold set of expectations for the Claude instructions but the init plugin should cover us.
|
What's the latest here? |
|
Those expectations were pulled from the linked confluence doc. Doing it this way allows us to remove confluence read requirements from automated initial documentation. I don't see anything in here I'd like to change, this was draft waiting on plugins to update and those are now moving again. I'm comfortable moving this forward again, now. |
Claude Code validationResult: Pass Reviewed the one changed Claude file, Not covered: The external link on line 8 ( |
2 participants
📔 Objective
Ensure compliance with new README requirements from the get-go. (see documentation standards PR)
This repository is only responsible for initializing repositories in a good state, so the actual long-term requirements of READMEs are kept in contributing-docs