You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are running the Locality-backed comparison benchmark.
2
+
3
+
User prompt:
4
+
i want you to analyze the progress made by different team members from July 15 to July 21 in the year 2025 on the repo codeflash-ai/codeflash , read the linear issues for that time range and read the notion doc named 'Company' and create a notion doc in the page title `Locality Launch` followed by the current date and time in the title to distinguish it which summarizes your findings. use `loc` , `git` and `gh` to fulfil the tasks, do not rely on notion or linear mcp or api calls.
5
+
6
+
Use only these context sources:
7
+
-`loc` commands
8
+
- local git commands in `REPO_DIR`
9
+
- GitHub context available through `gh`
10
+
- mounted Locality files under the paths listed in `CONTEXT_PATHS_FILE`
11
+
-`CONTEXT_INVENTORY`
12
+
-`CONTEXT_SEARCH_RESULTS`
13
+
-`OUT_DIR/git-data.json`
14
+
15
+
Do not use Notion MCP, Linear MCP, or direct Notion/Linear API tools in this run.
16
+
Do not push to Notion or update any remote source. For this benchmark, satisfy the requested Notion doc by writing the Markdown body to `OUT_DIR/report-body.md`.
17
+
18
+
Required work:
19
+
1. Read `OUT_DIR/git-data.json`.
20
+
2. Inspect relevant codeflash-ai/codeflash repository progress for July 15 through July 21, 2025 using git and `gh` where available.
21
+
3. Use `loc` and mounted Locality files to find and read relevant Notion context, including the doc named `Company` if available.
22
+
4. Use Locality-accessible context for Linear issue information if available; if Linear issues are not accessible through allowed sources, state that limitation.
23
+
5. Summarize progress by team member and connect it to the `Locality Launch` context where possible.
24
+
6. Write the final Markdown draft to `OUT_DIR/report-body.md`.
25
+
7. Write a compact trace to `OUT_DIR/locality-agent-trace.md` listing:
26
+
-`loc`, git, and gh commands used
27
+
- mounted Locality files read
28
+
- key facts used from Locality context
29
+
- unavailable or unverified Linear/Notion context
30
+
31
+
Report format:
32
+
33
+
# Locality Launch Team Progress Summary
34
+
35
+
## Summary
36
+
37
+
## Team Member Progress
38
+
39
+
## Linear Issue Context
40
+
41
+
## Company Context
42
+
43
+
## Launch Relevance
44
+
45
+
## Risks, Gaps, And Limitations
46
+
47
+
The draft should be concise, specific, and grounded in evidence. If a claim cannot be verified from loc, git, gh, or mounted Locality context, say so.
i want you to analyze the progress made by different team members from July 15 to July 21 in the year 2025 on the repo codeflash-ai/codeflash , read the linear issues for that time range and read the notion doc named 'Company' and create a notion doc in the page title `Locality Launch` followed by the current date and time in the title to distinguish it which summarizes your findings.
5
+
6
+
Use these context sources:
7
+
- local git commands in `REPO_DIR`
8
+
-`OUT_DIR/git-data.json`
9
+
- available MCP tools for Notion and Linear context
10
+
11
+
Do not read mounted Locality Notion files under `/home/amika/notion`.
12
+
Do not use `loc` commands.
13
+
Do not push or update Notion or any remote source in this run. For this benchmark, satisfy the requested Notion doc by writing the Markdown body to `OUT_DIR/notion-mcp-report-body.md`.
14
+
15
+
Required work:
16
+
1. Read `OUT_DIR/git-data.json`.
17
+
2. Inspect relevant codeflash-ai/codeflash repository progress for July 15 through July 21, 2025 using local git commands as needed.
18
+
3. Use MCP tools to read Linear issues for that time range if available.
19
+
4. Use MCP tools to find and read the Notion doc named `Company` if available.
20
+
5. Summarize progress by team member and connect it to the `Locality Launch` context where possible.
21
+
6. Write the final Markdown draft to `OUT_DIR/notion-mcp-report-body.md`.
22
+
7. Write a compact trace to `OUT_DIR/notion-mcp-agent-trace.md` listing:
23
+
- git commands used
24
+
- MCP searches/calls attempted
25
+
- Notion pages, Linear issues, or excerpts used
26
+
- limitations
27
+
28
+
Report format:
29
+
30
+
# Locality Launch Team Progress Summary
31
+
32
+
## Summary
33
+
34
+
## Team Member Progress
35
+
36
+
## Linear Issue Context
37
+
38
+
## Company Context
39
+
40
+
## Launch Relevance
41
+
42
+
## Risks, Gaps, And Limitations
43
+
44
+
The draft should be concise, specific, and grounded in evidence. If a claim cannot be verified from git or MCP context, say so.
0 commit comments