Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions .github/workflows/deep-report.lock.yml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

12 changes: 6 additions & 6 deletions .github/workflows/deep-report.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ safe-outputs:
expires: 2d
title-prefix: "[deep-report] "
labels: [automation, improvement, quick-win, cookie]
max: 3
max: 7
group: true

tools:
Expand Down Expand Up @@ -73,7 +73,7 @@ Continuously review and aggregate information from the various reports created a
3. **Flag interesting activity** - Highlight noteworthy discoveries, improvements, or anomalies
4. **Detect suspicious patterns** - Identify potential security concerns or concerning behaviors
5. **Surface exciting developments** - Celebrate wins, improvements, and positive trends
6. **Extract actionable tasks** - Identify exactly 3 specific, high-impact tasks that can be assigned to agents for quick wins
6. **Extract actionable tasks** - Identify exactly 7 specific, high-impact tasks that can be assigned to agents for quick wins

## Data Sources

Expand Down Expand Up @@ -217,7 +217,7 @@ Connect the dots between different data sources:

### Step 3.5: Extract Actionable Agentic Tasks

**CRITICAL**: Based on your analysis, identify exactly **3 actionable tasks** (quick wins) and **CREATE GITHUB ISSUES** for each one:
**CRITICAL**: Based on your analysis, identify exactly **7 actionable tasks** (quick wins) and **CREATE GITHUB ISSUES** for each one:

1. **Prioritize by impact and effort**: Look for high-impact, low-effort improvements
2. **Be specific**: Tasks should be concrete with clear success criteria
Expand Down Expand Up @@ -300,7 +300,7 @@ Based on trend analysis, provide:

### ✅ Actionable Agentic Tasks (Quick Wins)

**CRITICAL**: Identify exactly **3 actionable tasks** that could be immediately assigned to an AI agent to improve the project. Focus on **quick wins** - tasks that are:
**CRITICAL**: Identify exactly **7 actionable tasks** that could be immediately assigned to an AI agent to improve the project. Focus on **quick wins** - tasks that are:
Copy link

Copilot AI Apr 13, 2026

Choose a reason for hiding this comment

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

The instructions conflict: this line requires identifying exactly 7 actionable tasks, but later the prompt allows identifying none (and instructs calling noop). To avoid agent confusion/failed runs, consider changing this requirement to "up to 7" (or "at most 7"), and keep the rest of the section consistent with that wording.

This issue also appears on line 360 of the same file.

Suggested change
**CRITICAL**: Identify exactly **7 actionable tasks** that could be immediately assigned to an AI agent to improve the project. Focus on **quick wins** - tasks that are:
**CRITICAL**: Identify up to **7 actionable tasks** that could be immediately assigned to an AI agent to improve the project. Focus on **quick wins** - tasks that are:

Copilot uses AI. Check for mistakes.
- **Specific and well-defined** - Clear scope with measurable outcome
- **Achievable by an agent** - Can be automated or assisted by AI
- **High impact, low effort** - Maximum benefit with minimal implementation time
Expand Down Expand Up @@ -328,7 +328,7 @@ Based on trend analysis, provide:
- "Optimize token usage in verbose agent prompts (identified 4 candidates)"
- "Add missing documentation for 2 frequently-used MCP tools"

**Remember**: The maximum is 3 issues. Choose the most impactful tasks.
**Remember**: The maximum is 7 issues. Choose the most impactful tasks.

### 📚 Source Attribution

Expand Down Expand Up @@ -357,7 +357,7 @@ List all reports and data sources analyzed:

## Final Steps

1. **Create GitHub Issues**: For each of the 3 actionable tasks identified (if any), create a GitHub issue using the safe-outputs create-issue capability
1. **Create GitHub Issues**: For each of the 7 actionable tasks identified (if any), create a GitHub issue using the safe-outputs create-issue capability
2. **Create Discussion Report**: Create a new GitHub discussion titled "DeepReport Intelligence Briefing - [Today's Date]" in the "reports" category with your full analysis (including the identified actionable tasks)

**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
Expand Down
Loading