Hugging Face's logo

Datasets:
armand0e
/
badlogicgames-pi-mono-opus-filtered

Modalities:
Tabular
Text
Formats:
json
Traces
Size:
< 1K
Tags:
agent-traces
pi
coding-agent
distillation
claude
opus
Libraries:
Datasets
Dask
Polars
Dataset card Data Studio Files
xet
 Community
Pi traces preview
Fri, Jan 16
Analyze GitHub issue(s): https://github.com/badlogic/pi-mono/issues/784 test in docker locally, temp container For each issue: 1. Read the issue in full, including all comments and linked issues/PRs. 2. **For bugs**: - Ignore any root cause analysis in the issue (likely wrong) - Read all related code files in full (no truncation) - Trace the code path and identify the actual root cause - Propose a fix 3. **For feature requests**: - Read all related code files in full (no truncation) - Propose the most concise implementation approach - List affected files and changes needed Do NOT implement unless explicitly asked. Analyze and propose only. 16 messages 122 tools we added a env var for cursor, we need to invert the logic, only use the hardware cursor if the env var is set 6 messages 52 tools hi yeah, this is nice 1 message 1 tool You are given one or more GitHub PR URLs: https://github.com/badlogic/pi-mono/pull/775 For each PR URL, do the following in order: 1. Read the PR page in full. Include description, all comments, all commits, and all changed files. 2. Identify any linked issues referenced in the PR body, comments, commit messages, or cross links. Read each issue in full, including all comments. 3. Analyze the PR diff. Read all relevant code files in full with no truncation from the current main branch and compare against the diff. Do not fetch PR file blobs unless a file is missing on main or the diff context is insufficient. Include related code paths that are not in the diff but are required to validate behavior. 4. Check for a changelog entry in the relevant `packages/*/CHANGELOG.md` files. Report whether an entry exists. If missing, state that a changelog entry is required before merge and that you will add it if the user decides to merge. Follow the changelog format rules in AGENTS.md. Verify: - Entry uses correct section (`### Breaking Changes`, `### Added`, `### Fixed`, etc.) - External contributions include PR link and author: `Fixed foo ([#123](https://github.com/badlogic/pi-mono/pull/123) by [@user](https://github.com/user))` - Breaking changes are in `### Breaking Changes`, not just `### Fixed` 5. Check if packages/coding-agent/README.md, packages/coding-agent/docs/*.md, packages/coding-agent/examples/**/*.md require modification. This is usually the case when existing features have been changed, or new features have been added. 6. Provide a structured review with these sections: - Good: solid choices or improvements - Bad: concrete issues, regressions, missing tests, or risks - Ugly: subtle or high impact problems 7. Add Questions or Assumptions if anything is unclear. 8. Add Change summary and Tests. Output format per PR: PR: <url> Changelog: - ... Good: - ... Bad: - ... Ugly: - ... Questions or Assumptions: - ... Change summary: - ... Tests: - ... If no issues are found, say so under Bad and Ugly. 3 messages 28 tools Analyze GitHub issue(s): https://github.com/badlogic/pi-mono/issues/774 For each issue: 1. Read the issue in full, including all comments and linked issues/PRs. 2. **For bugs**: - Ignore any root cause analysis in the issue (likely wrong) - Read all related code files in full (no truncation) - Trace the code path and identify the actual root cause - Propose a fix 3. **For feature requests**: - Read all related code files in full (no truncation) - Propose the most concise implementation approach - List affected files and changes needed Do NOT implement unless explicitly asked. Analyze and propose only. 3 messages 18 tools You are given one or more GitHub PR URLs: https://github.com/badlogic/pi-mono/pull/765 For each PR URL, do the following in order: 1. Read the PR page in full. Include description, all comments, all commits, and all changed files. 2. Identify any linked issues referenced in the PR body, comments, commit messages, or cross links. Read each issue in full, including all comments. 3. Analyze the PR diff. Read all relevant code files in full with no truncation from the current main branch and compare against the diff. Do not fetch PR file blobs unless a file is missing on main or the diff context is insufficient. Include related code paths that are not in the diff but are required to validate behavior. 4. Check for a changelog entry in the relevant `packages/*/CHANGELOG.md` files. Report whether an entry exists. If missing, state that a changelog entry is required before merge and that you will add it if the user decides to merge. Follow the changelog format rules in AGENTS.md. Verify: - Entry uses correct section (`### Breaking Changes`, `### Added`, `### Fixed`, etc.) - External contributions include PR link and author: `Fixed foo ([#123](https://github.com/badlogic/pi-mono/pull/123) by [@user](https://github.com/user))` - Breaking changes are in `### Breaking Changes`, not just `### Fixed` 5. Check if packages/coding-agent/README.md, packages/coding-agent/docs/*.md, packages/coding-agent/examples/**/*.md require modification. This is usually the case when existing features have been changed, or new features have been added. 6. Provide a structured review with these sections: - Good: solid choices or improvements - Bad: concrete issues, regressions, missing tests, or risks - Ugly: subtle or high impact problems 7. Add Questions or Assumptions if anything is unclear. 8. Add Change summary and Tests. Output format per PR: PR: <url> Changelog: - ... Good: - ... Bad: - ... Ugly: - ... Questions or Assumptions: - ... Change summary: - ... Tests: - ... If no issues are found, say so under Bad and Ugly. 2 messages 25 tools alright, time for a new release. i want you to: - check if all third party contributions since the last release have changelog entries (!= badlogic == me) - check if CHANGELOG.md entries of packages != coding-agent but that affect coding-agent are also in the CHANGELOG.md of the coding-agent - tell me if we are good to release 5 messages 29 tools ok, do some stuff 1 message 3 tools You are given one or more GitHub PR URLs: https://github.com/badlogic/pi-mono/pull/719 For each PR URL, do the following in order: 1. Read the PR page in full. Include description, all comments, all commits, and all changed files. 2. Identify any linked issues referenced in the PR body, comments, commit messages, or cross links. Read each issue in full, including all comments. 3. Analyze the PR diff. Read all relevant code files in full with no truncation from the current main branch and compare against the diff. Do not fetch PR file blobs unless a file is missing on main or the diff context is insufficient. Include related code paths that are not in the diff but are required to validate behavior. 4. Check for a changelog entry in the relevant `packages/*/CHANGELOG.md` files. Report whether an entry exists. If missing, state that a changelog entry is required before merge and that you will add it if the user decides to merge. Follow the changelog format rules in AGENTS.md. Verify: - Entry uses correct section (`### Breaking Changes`, `### Added`, `### Fixed`, etc.) - External contributions include PR link and author: `Fixed foo ([#123](https://github.com/badlogic/pi-mono/pull/123) by [@user](https://github.com/user))` - Breaking changes are in `### Breaking Changes`, not just `### Fixed` 5. Check if packages/coding-agent/README.md, packages/coding-agent/docs/*.md, packages/coding-agent/examples/**/*.md require modification. This is usually the case when existing features have been changed, or new features have been added. 6. Provide a structured review with these sections: - Good: solid choices or improvements - Bad: concrete issues, regressions, missing tests, or risks - Ugly: subtle or high impact problems 7. Add Questions or Assumptions if anything is unclear. 8. Add Change summary and Tests. Output format per PR: PR: <url> Changelog: - ... Good: - ... Bad: - ... Ugly: - ... Questions or Assumptions: - ... Change summary: - ... Tests: - ... If no issues are found, say so under Bad and Ugly. 13 messages 75 tools hello 1 message

Filtered version of badlogicgames/pi-mono - Only opus traces, dropped invalid sessions as well.

All traces present are training safe and teich compatible
Downloads last month
362
Number of rows:
182
Total file size:
33.5 MB

Models trained or fine-tuned on armand0e/badlogicgames-pi-mono-opus-filtered