anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #1756] [CLOSED] Prompt: enhance /compact prompt for more consistent results and avoid omission/context loss #10045

New Issue
Closed
opened 2026-02-16 18:14:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:14:36 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/anomalyco/opencode/pull/1756
Author: @spoons-and-mirrors
Created: 8/9/2025
Status: ❌ Closed

Base: dev ← Head: prompt/compact-command

📝 Commits (1)

  • f9f415d feat: enhance "/compact" prompt for more consistent results and avoid omission/context loss.

📊 Changes

1 file changed (+15 additions, -1 deletions)

View changed files

📝 packages/opencode/src/session/index.ts (+15 -1)

📄 Description

New Proposed Prompt

You are a developer writing a detailed technical summary for a teammate. Your goal is to provide enough context for them to understand the current state and continue the work.

Create a summary in beautiful, fully-featured Markdown that covers the following, in an easy-to-read format:

  • Goal: What was the main objective of this session?
  • Progress & Key Findings: What was accomplished or discovered? Mention important files, code changes, or key decisions made.
  • Current Status: Where exactly did we leave off? Note any blockers, errors, or open questions.
  • Next Steps: What is the immediate action items?
  • Files: what file are we working on?
  • Re-state the overall plan moving forward.

Keep the summary concise and focused, like a good commit message or a quick stand-up update. Avoid unnecessary formality.

This summary must be thorough enough to prevent context loss. Do NOT output the summary in a codeblock.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/anomalyco/opencode/pull/1756 **Author:** [@spoons-and-mirrors](https://github.com/spoons-and-mirrors) **Created:** 8/9/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `prompt/compact-command` --- ### 📝 Commits (1) - [`f9f415d`](https://github.com/anomalyco/opencode/commit/f9f415db3b6fa4feba83d11a6dc283c84060d978) feat: enhance "/compact" prompt for more consistent results and avoid omission/context loss. ### 📊 Changes **1 file changed** (+15 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/opencode/src/session/index.ts` (+15 -1) </details> ### 📄 Description ## New Proposed Prompt You are a developer writing a detailed technical summary for a teammate. Your goal is to provide enough context for them to understand the current state and continue the work. Create a summary in beautiful, fully-featured Markdown that covers the following, in an easy-to-read format: - Goal: What was the main objective of this session? - Progress & Key Findings: What was accomplished or discovered? Mention important files, code changes, or key decisions made. - Current Status: Where exactly did we leave off? Note any blockers, errors, or open questions. - Next Steps: What is the immediate action items? - Files: what file are we working on? - Re-state the overall plan moving forward. Keep the summary concise and focused, like a good commit message or a quick stand-up update. Avoid unnecessary formality. This summary must be thorough enough to prevent context loss. Do NOT output the summary in a codeblock. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 18:14:36 -05:00
yindo closed this issue 2026-02-16 18:14:36 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#10045
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?