chore: adopt repo-standard, stage=in-progress (#46) - #50
Conversation
Every other required in-progress-tier artifact (AGENTS.md, README.md, specs/, specs/decisions/, .specify/, .specify/memory/constitution.md, tasks/) already exists, per the issue's own audit table — repo.toml was the one missing piece. Co-authored-by: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR adopts the repository-standard by introducing a repo stage configuration file that marks the project as "in-progress", with all other required artifacts already present and verified manually. File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Warning Review limit reached
Next review available in: 118 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
Summary
tasks/issue-46-chore-adopt-repo-standard-stage-in-progress.md(issue chore: adopt repo-standard (stage=in-progress) #46): addsrepo.tomlwithstage = "in-progress".in-progress-tier artifact already exists (AGENTS.md,README.md,specs/,specs/decisions/,.specify/,.specify/memory/constitution.md,tasks/) — verified by hand againstrepo-standard's required-paths table since the skill itself isn't invocable from this repo.Test plan
in-progress— all presentstage = "in-progress"is one of the four valid enum values (prototype/in-progress/released/archived)make build/make testgreen (config-only change, no Rust code touched)🧙 Built with WOZCODE
Summary by Sourcery
Chores:
Summary by cubic
Declares repository stage in
repo.tomlas "in-progress" to comply with repo-standard and enable tooling that reads stage. Previously the repo had no declared stage; now it does. No runtime or build behavior changes.repo.tomlwithstage = "in-progress".AGENTS.md,README.md,specs/,specs/decisions/,.specify/,.specify/memory/constitution.md,tasks/.make buildandmake testremain green.Written for commit ae67212. Summary will update on new commits.