feat: release v1.2.0 — merged v1.0.0 depth with v1.1.0 improvements

[webDarts]

What's New in v1.2.0

This release merges the depth of the original v1.0.0 skill with the improvements from v1.1.0.

Key Changes

• Full 10-step pipeline restored — Memory Check → Discovery → Analysis → Phase Detection → Skill Mapping → Session Plan → Execution → Monitoring → Verification → Completion
• Step 0: Memory Check — reads .agents/memory/MEMORY.md before any work
• MCP-aware discovery — scans for Codegraph, Context7, and Playwright MCP servers with usage guidance
• Codegraph integration — uses codegraph_search, codegraph_context, codegraph_impact before writing/editing code
• Hybrid prompt generation — 6 phase templates (Planning, Implementation, Testing, Review, Debug, Ship)
• Enhanced error recovery — Root Cause Analysis, Incremental Rollback, Graceful Degradation patterns
• Expanded monitoring — added Rust (cargo) and Go to the build/typecheck table
• Parallel execution — clear guidance on when to use Agent tool with run_in_background: true
• Context budget rule — never read more than 10 files per turn; use Codegraph or Explore subagent
• Session plan checkpoint — .local/session_plan.md with resume-from-checkpoint support
• Output manifest & follow-up tasks — tracks artifacts and proposes next steps
• Approval gates — pauses for destructive actions (schema drops, bulk deletes, major swaps)

Files Changed

• skills/autopilot/SKILL.md — complete rewrite merging both versions
• package.json — bumped to 1.2.0
• CHANGELOG.md — added v1.2.0 entry
• README.md — updated features and pipeline
• examples/ — updated with Codegraph and new patterns
• CONTRIBUTING.md — updated project layout and release process

[coderabbitai]

Warning

Review limit reached

@webDarts, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes and 24 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2de30d37-ed14-4800-b07f-8c0a863a0048

📥 Commits

Reviewing files that changed from the base of the PR and between fcafd19 and 22ea213.

📒 Files selected for processing (8)

• CHANGELOG.md
• CONTRIBUTING.md
• README.md
• examples/basic-usage.md
• examples/full-project.md
• package.json
• skills/autopilot/.version
• skills/autopilot/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}