tweak prompt, add GH App idea

Author: sayansisodiya

IDEA.md

@@ -0,0 +1,52 @@
+# Ideas for CRA-GitHub
+
+## Action-Only GitHub App for Custom Branding
+
+### Problem
+Current workflow uses `GITHUB_TOKEN` which always posts reviews as "github-actions[bot]" with generic avatar. No way to customize the identity.
+
+### Solution: Action-Only GitHub App
+Create a GitHub App that provides authentication tokens to workflows without requiring hosted webhooks.
+
+**Key Insight**: GitHub Apps can be used purely for identity/authentication in workflows without needing a 24/7 server.
+
+### Implementation
+1. **Create GitHub App** with custom name ("Amp Code Review") and logo
+2. **Configure permissions**: Pull requests (write), Checks (write), Contents (read)
+3. **No webhook URL needed** - app only provides tokens
+4. **Update workflow** to use `actions/create-github-app-token@v1`
+5. **Users install app + copy modified workflow**
+
+### Benefits
+- ✅ Custom branding ("Amp Code Review[bot]" with logo)
+- ✅ No hosting infrastructure required
+- ✅ Same compute model (runs on user's GitHub Actions)
+- ✅ Backwards compatible (can offer both options)
+
+### User Setup
+1. Install "Amp Code Review" GitHub App on repo
+2. Set secrets: `AMP_APP_ID`, `AMP_PRIVATE_KEY`, `AMP_API_KEY`
+3. Copy modified workflow that generates app token
+4. Reviews appear with custom branding
+
+### Modified Workflow
+```yaml
+steps:
+  - uses: actions/create-github-app-token@v1
+    id: app-token
+    with:
+      app-id: ${{ secrets.AMP_APP_ID }}
+      private-key: ${{ secrets.AMP_PRIVATE_KEY }}
+
+  - name: Run Amp Code Review
+    uses: docker://ghcr.io/sourcegraph/cra-github:latest
+    env:
+      GITHUB_TOKEN: ${{ steps.app-token.outputs.token }}  # App token
+      AMP_SERVER_URL: ${{ vars.AMP_SERVER_URL }}
+      AMP_API_KEY: ${{ secrets.AMP_API_KEY }}
+```
+
+### Trade-offs
+- **Pro**: Custom branding without hosting costs
+- **Con**: Slightly more complex user setup (install app + workflow)
+- **Pro**: Can coexist with current simple approach

config.yml

@@ -56,7 +56,6 @@ amp:
     After you have completed the code review process, leave a single general comment.
     This comment should NOT reiterate the issues already identified in inline comments. Instead, include:
     * A brief summary of the diff's changes; include the goal of the changes and what they affect
-    * A tour of the changes-- recommend the best tour order for reviewing the changes. Identify the best place to start the review-— the part that conveys the core and helps in understanding the rest.
     * (Optional) Any minor or vague considerations that were not obvious enough to be left as an inline comment-- don't repeat any inline comments.
 
     Keep your tone professional and concise when commenting. No emojis.