doc(devbird): Move docs

[kdy1]

No description provided.

[Copilot]

Pull Request Overview

This PR reorganizes documentation by moving the "Multiple concurrent PRs" section from the PR review guide to the composite tasks troubleshooting guide. The change improves documentation structure by placing information about concurrent PRs alongside composite task documentation where it's more contextually relevant.

• Moved "Multiple concurrent PRs" section from reviewing-prs/index.mdx to troubleshooting/composite-task.mdx
• Updated warning text in composite-task.mdx to clarify scope of under-review content

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
devbird/reviewing-prs/index.mdx	Removed "Multiple concurrent PRs" section
devbird/troubleshooting/composite-task.mdx	Added "Multiple concurrent PRs" section and updated warning text

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[claude]

PR Review

Summary

This PR moves the "Multiple concurrent PRs" section from the PR review documentation () to the troubleshooting documentation for composite tasks ().

---

✅ Positive Aspects

1. Better information architecture: Moving concurrent PR documentation to troubleshooting makes sense, as this is more of an expected behavior/FAQ topic rather than core PR review workflow documentation.

2. Maintains frontmatter: Both files have proper frontmatter with title and description fields.

3. Preserves content: The section content is moved intact without losing information.

4. Adds context with warning: The placement before the warning tag helps set expectations for users, positioning it as "this is normal" before diving into actual troubleshooting content.

---

📋 Recommendations

1. Content placement concern

The "Multiple concurrent PRs" section now appears at the top of a troubleshooting document, but this content describes expected behavior rather than a problem to troubleshoot. Consider one of these alternatives:

Option A (Recommended): Move to a concepts or FAQ section instead

• This isn't really troubleshooting content—it's explaining normal system behavior
• Would fit better in a general concepts doc or dedicated FAQ page

Option B: Keep in troubleshooting but reframe the heading

## Understanding Concurrent PRs (This is Expected Behavior)

This makes it clearer that users didn't stumble upon a problem.

Option C: Add a note at the beginning of troubleshooting section

> **Note**: DevBird creating multiple PRs simultaneously is expected behavior. See the section below for more information.

2. Document structure considerations

The placement interrupts the flow of the composite-task troubleshooting document:

• The original intro at line 23 ("This guide helps you troubleshoot...") now appears after the concurrent PRs section
• This creates a disjointed reading experience

Suggested fix: Either move concurrent PRs to the end, or move it to a different document entirely.

3. Cross-references

Since this content was moved, consider:

• Adding a brief mention in the original location with a link: "DevBird may create multiple PRs for different tasks—learn more"
• Checking if any other pages link to this section and need updating

4. Title/Description update consideration

The troubleshooting page description says "Common issues with composite tasks and task graphs" but now includes content about expected behavior. Consider updating the description to reflect this.

---

✅ Code Quality Assessment

• No code changes: This is a documentation-only change
• No security concerns: Moving static documentation content
• No performance impact: Static content reorganization
• No test coverage needed: Documentation changes

---

🎯 Alignment with CLAUDE.md

✅ Uses MDX format with YAML frontmatter
✅ Maintains proper frontmatter structure
✅ No absolute URLs introduced
✅ Content remains accurate
⚠️ Consider: The CLAUDE.md states "Start by making the smallest reasonable changes"—this is a small change, but consider if the destination document is the optimal location.

---

Final Recommendation

Approve with suggestions: The PR is technically correct and won't break anything, but the content placement could be optimized for better user experience. Consider:

1. Evaluating if troubleshooting is the right home for "expected behavior" documentation
2. If keeping in troubleshooting, adjust the document structure to improve flow
3. Add cross-reference in the original location

The change is safe to merge as-is, but addressing the placement concern would improve documentation quality.