feat: rewrite org profile for non-crypto developers#7
Conversation
|
Caution Review failedFailed to post review comments 📝 WalkthroughWalkthroughThe profile README is reorganized to prioritize marketing and hands-on usage: a "$2 free credit" callout and Vendor Marketplace appear near the top, followed by updated repos and quickstart snippets demonstrating ChangesDocumentation Restructuring for Marketing and Usage
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Rewrites the org profile README to target developers unfamiliar with crypto, stripping protocol-level details and focusing on a simple "what it does → install → call" flow.
Changes:
- Replaces the protocol/stack tables (ERC-8004, LTV, facilitator addresses, etc.) with a 3-step "What Floe does" section.
- Adds a vendor marketplace table (27 endpoints) and a simple curl example for a paid API call.
- Condenses install, repos, framework support, and footer links into briefer sections.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…ternals Add Vendor Marketplace section (27 verified endpoints, 7 categories). Remove protocol internals (contract addresses, LTV ratios, facilitator EOA, matcher proxy, oracle details, ERC-8004 spec references) — these belong in docs, not the org profile. Keep: framework table, code examples (TS/Python/MCP), stack table, repos, links, $2 free credit CTA. Reword stack table to avoid crypto jargon: "on-chain collateral" → "your deposit", "ERC-8004 identity" → removed, "per-loan isolated escrow" → removed.
c2b7afe to
d1b3ee5
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@profile/README.md`:
- Around line 55-58: The fenced code block starting with "```bash" in README.md
lacks a preceding blank line; insert a single blank line immediately before that
fenced code block (the line containing "```bash") so the Markdown renderer
treats the block correctly and follows Markdown best practices.
- Around line 60-63: Add a blank line immediately before the fenced code block
starting with ```bash that contains "pip install floe-agentkit-actions" so the
Markdown has an empty line separating the preceding paragraph and the code
block; update the README.md so the fenced block is preceded by one blank line
(and ensure there is still a closing ``` after the command).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 6d6b4917-377b-4a20-a338-c4686a63c094
📒 Files selected for processing (1)
profile/README.md
|
@copilot resolve the merge conflicts in this pull request |
Strip all protocol details (contract addresses, LTV ratios, ERC-8004, matcher proxy, facilitator EOA, intent matching, oracle details). None of that matters to someone evaluating whether to use Floe.
New structure: what it does (3 steps) → vendor marketplace (27 endpoints) → install (3 lines) → make a call (one curl) → repos → frameworks. Developer lands, understands, installs.
Summary by CodeRabbit