Skip to content

docs: add 5-minute quick start section to README#168

Merged
iap merged 6 commits into
devfrom
feat/improve-readme-quick-start
May 19, 2026
Merged

docs: add 5-minute quick start section to README#168
iap merged 6 commits into
devfrom
feat/improve-readme-quick-start

Conversation

@iap

@iap iap commented May 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Improves new contributor onboarding with a clear, fast quick start.

Changes

  • Prerequisites check: Version requirements for Node/pnpm/Foundry
  • One-command setup: pnpm i && pnpm dev
  • What Just Happened: Explains what the setup did
  • Next Steps: Links to CONTRIBUTING, CHANGELOG, contract docs
  • Detailed Setup: Kept for reference

Before/After

Before: Generic "Getting Started" with no version checks
After: Clear 5-minute path with prerequisites validation

Verification

Tested locally - all links work, commands are accurate.

Risk

None - documentation only.

Related

  • Part of Phase 1 improvement plan (Week 1, Day 5)

iap added 2 commits May 19, 2026 11:30
- Add CHANGELOG.md with current deployment state
- Add CONTRIBUTORS.md for community recognition
- Add GitHub issue templates (bug report, feature request)
- Enables structured community contributions
- Add prerequisites check with version requirements
- Add one-command setup for fast onboarding
- Add 'What Just Happened' section for clarity
- Link to CONTRIBUTING, CHANGELOG, and contract docs
- Keep detailed setup section for reference

Improves new contributor onboarding experience.
@iap iap requested a review from a team as a code owner May 19, 2026 05:05
@github-actions

github-actions Bot commented May 19, 2026

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@greptile-apps

greptile-apps Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds a "Quick Start (5 minutes)" section to the README to improve new-contributor onboarding with prerequisite checks, a one-command setup, and next-step links, while renaming the existing "Getting Started" block to "Detailed Setup."

  • The three linked files (CONTRIBUTING.md, CHANGELOG.md, contracts/README.md) all exist in the repository, so the Next Steps links are valid.
  • Several inaccuracies in the new section (contract-deployment claim, .nvmrc reference, Node version constraint narrower than package.json engines) were identified and flagged in prior review threads; those items remain unaddressed in the current state of the file.

Confidence Score: 5/5

Documentation-only change with no code modifications; no new issues identified beyond those already raised in prior review threads.

All the inaccuracies in the new Quick Start section (contract deployment claim, missing .nvmrc file, node version constraint, ambiguous Foundry version check) were surfaced and discussed in earlier review rounds. The corepack prepare pnpm@9.0.2 --activate instruction now includes an explicit version pin, which resolves the one prior concern that has since been addressed. No new defects were found in this pass.

README.md — the previously-flagged inaccuracies are still present in the file and worth resolving before the Quick Start is relied upon by contributors.

Important Files Changed

Filename Overview
README.md Adds Quick Start section; previously-flagged inaccuracies (contract deployment claim, missing .nvmrc, node version constraint) remain unresolved in the file.

Reviews (5): Last reviewed commit: "Merge branch 'dev' into feat/improve-rea..." | Re-trigger Greptile

Comment thread README.md Outdated
Comment thread README.md

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c6b6412f35

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
Comment thread README.md Outdated
Comment thread README.md
Greptile review caught that 'corepack prepare' without a version
will fail before the repo is cloned (no package.json to read from).

Now: corepack prepare pnpm@9.0.2 --activate
Comment thread README.md
Comment thread README.md
Comment thread README.md
@iap iap merged commit 366025a into dev May 19, 2026
17 checks passed
@iap iap deleted the feat/improve-readme-quick-start branch May 19, 2026 13:26
iap added a commit that referenced this pull request May 19, 2026
…172)

- Fix: Remove outdated .nvmrc reference in README (now using mise)
- Fix: Update PoseidonT3.sol Solidity version from ^0.8.24 to ^0.8.25
- Docs: Update CHANGELOG with recent merged PRs (#170, #169, #168, #163)
- Refactor: Move documentation to docs/ directory for better organization
- Update README links to reflect new docs/ structure
iap added a commit that referenced this pull request May 19, 2026
…#173)

* chore: fix typo, bug, update docs, and reorganize project structure

- Fix: Remove outdated .nvmrc reference in README (now using mise)
- Fix: Update PoseidonT3.sol Solidity version from ^0.8.24 to ^0.8.25
- Docs: Update CHANGELOG with recent merged PRs (#170, #169, #168, #163)
- Refactor: Move documentation to docs/ directory for better organization
  - CONTRIBUTING.md -> docs/CONTRIBUTING.md
  - BRANCHING.md -> docs/BRANCHING.md
  - DEPLOYMENT.md -> docs/DEPLOYMENT.md
  - TROUBLESHOOTING.md -> docs/TROUBLESHOOTING.md
  - Copy THREAT_MODEL.md, KNOWN_ISSUES.md, ARCHITECTURE.md to docs/
- Update README links to reflect new docs/ structure

* chore(contracts): set EVM version to paris for OP Stack compatibility

- Add evm_version = "paris" to foundry.toml
- Ensures bytecode compatibility with Optimism Superchain
- Paris is the EVM version used by OP Mainnet and OP Sepolia
- All 148 tests pass with Paris EVM

* chore: update gas snapshot for paris EVM version

Gas costs increased by ~3-5% after switching to paris EVM target.
This is expected behavior for OP Stack compatibility.
iap added a commit that referenced this pull request May 20, 2026
…174)

* chore: fix typo, bug, update docs, and reorganize project structure

- Fix: Remove outdated .nvmrc reference in README (now using mise)
- Fix: Update PoseidonT3.sol Solidity version from ^0.8.24 to ^0.8.25
- Docs: Update CHANGELOG with recent merged PRs (#170, #169, #168, #163)
- Refactor: Move documentation to docs/ directory for better organization
  - CONTRIBUTING.md -> docs/CONTRIBUTING.md
  - BRANCHING.md -> docs/BRANCHING.md
  - DEPLOYMENT.md -> docs/DEPLOYMENT.md
  - TROUBLESHOOTING.md -> docs/TROUBLESHOOTING.md
  - Copy THREAT_MODEL.md, KNOWN_ISSUES.md, ARCHITECTURE.md to docs/
- Update README links to reflect new docs/ structure

* chore(contracts): set EVM version to paris for OP Stack compatibility

- Add evm_version = "paris" to foundry.toml
- Ensures bytecode compatibility with Optimism Superchain
- Paris is the EVM version used by OP Mainnet and OP Sepolia
- All 148 tests pass with Paris EVM

* refactor(deps): replace createx with direct openzeppelin dependency

- Install OpenZeppelin v5.1.0 as direct git submodule
- Remove createx dependency (only used for nested OZ)
- Remove unused DeployUtils.sol library
- Update remappings: @openzeppelin/=lib/openzeppelin-contracts/
- Consolidate all remappings to foundry.toml
- Remove root remappings.txt to avoid conflicts
- Add forge-std/ remapping for completeness
- Clean forge cache and verify build

Benefits:
- Smaller dependency tree (3 deps instead of 4)
- Direct control over OpenZeppelin version
- No nested dependencies
- Single source of truth for remappings

Verified:
- forge build: success
- forge test: 159 tests passed

* fix(docs): use consistent MAINNET_RPC variable in deployment guide

Address CodeRabbit feedback: line 488 used generic $RPC instead of
$MAINNET_RPC. Since this is in the Mainnet Deployment section and
the previous line uses $MAINNET_RPC, update for consistency.
@trade trade deleted a comment from coderabbitai Bot May 25, 2026
iap added a commit that referenced this pull request Jun 2, 2026
* docs: add changelog, contributors, and issue templates

- Add CHANGELOG.md with current deployment state
- Add CONTRIBUTORS.md for community recognition
- Add GitHub issue templates (bug report, feature request)
- Enables structured community contributions

* docs: add 5-minute quick start section to README

- Add prerequisites check with version requirements
- Add one-command setup for fast onboarding
- Add 'What Just Happened' section for clarity
- Link to CONTRIBUTING, CHANGELOG, and contract docs
- Keep detailed setup section for reference

Improves new contributor onboarding experience.

* fix: add version to corepack prepare command

Greptile review caught that 'corepack prepare' without a version
will fail before the repo is cloned (no package.json to read from).

Now: corepack prepare pnpm@9.0.2 --activate
iap added a commit that referenced this pull request Jun 2, 2026
…172)

- Fix: Remove outdated .nvmrc reference in README (now using mise)
- Fix: Update PoseidonT3.sol Solidity version from ^0.8.24 to ^0.8.25
- Docs: Update CHANGELOG with recent merged PRs (#170, #169, #168, #163)
- Refactor: Move documentation to docs/ directory for better organization
- Update README links to reflect new docs/ structure
iap added a commit that referenced this pull request Jun 2, 2026
…#173)

* chore: fix typo, bug, update docs, and reorganize project structure

- Fix: Remove outdated .nvmrc reference in README (now using mise)
- Fix: Update PoseidonT3.sol Solidity version from ^0.8.24 to ^0.8.25
- Docs: Update CHANGELOG with recent merged PRs (#170, #169, #168, #163)
- Refactor: Move documentation to docs/ directory for better organization
  - CONTRIBUTING.md -> docs/CONTRIBUTING.md
  - BRANCHING.md -> docs/BRANCHING.md
  - DEPLOYMENT.md -> docs/DEPLOYMENT.md
  - TROUBLESHOOTING.md -> docs/TROUBLESHOOTING.md
  - Copy THREAT_MODEL.md, KNOWN_ISSUES.md, ARCHITECTURE.md to docs/
- Update README links to reflect new docs/ structure

* chore(contracts): set EVM version to paris for OP Stack compatibility

- Add evm_version = "paris" to foundry.toml
- Ensures bytecode compatibility with Optimism Superchain
- Paris is the EVM version used by OP Mainnet and OP Sepolia
- All 148 tests pass with Paris EVM

* chore: update gas snapshot for paris EVM version

Gas costs increased by ~3-5% after switching to paris EVM target.
This is expected behavior for OP Stack compatibility.
iap added a commit that referenced this pull request Jun 2, 2026
…174)

* chore: fix typo, bug, update docs, and reorganize project structure

- Fix: Remove outdated .nvmrc reference in README (now using mise)
- Fix: Update PoseidonT3.sol Solidity version from ^0.8.24 to ^0.8.25
- Docs: Update CHANGELOG with recent merged PRs (#170, #169, #168, #163)
- Refactor: Move documentation to docs/ directory for better organization
  - CONTRIBUTING.md -> docs/CONTRIBUTING.md
  - BRANCHING.md -> docs/BRANCHING.md
  - DEPLOYMENT.md -> docs/DEPLOYMENT.md
  - TROUBLESHOOTING.md -> docs/TROUBLESHOOTING.md
  - Copy THREAT_MODEL.md, KNOWN_ISSUES.md, ARCHITECTURE.md to docs/
- Update README links to reflect new docs/ structure

* chore(contracts): set EVM version to paris for OP Stack compatibility

- Add evm_version = "paris" to foundry.toml
- Ensures bytecode compatibility with Optimism Superchain
- Paris is the EVM version used by OP Mainnet and OP Sepolia
- All 148 tests pass with Paris EVM

* refactor(deps): replace createx with direct openzeppelin dependency

- Install OpenZeppelin v5.1.0 as direct git submodule
- Remove createx dependency (only used for nested OZ)
- Remove unused DeployUtils.sol library
- Update remappings: @openzeppelin/=lib/openzeppelin-contracts/
- Consolidate all remappings to foundry.toml
- Remove root remappings.txt to avoid conflicts
- Add forge-std/ remapping for completeness
- Clean forge cache and verify build

Benefits:
- Smaller dependency tree (3 deps instead of 4)
- Direct control over OpenZeppelin version
- No nested dependencies
- Single source of truth for remappings

Verified:
- forge build: success
- forge test: 159 tests passed

* fix(docs): use consistent MAINNET_RPC variable in deployment guide

Address CodeRabbit feedback: line 488 used generic $RPC instead of
$MAINNET_RPC. Since this is in the Mainnet Deployment section and
the previous line uses $MAINNET_RPC, update for consistency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant