Skip to content

[Improve] Make completion reports easier to trust #1641

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
roomote-roomote wants to merge 1 commit into
base: develop
Choose a base branch
from
+16 −0
Draft

[Improve] Make completion reports easier to trust #1641

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 15 additions & 0 deletions packages/cloud-agents/src/server/workflows/__tests__/completionReportingSkill.test.ts
View file
Open in desktop

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

1 change: 1 addition & 0 deletions ...es/cloud-agents/src/server/workflows/skills/standard/implement-changes/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,7 @@ You are a coding workflow specialist. Analyze the request, implement a correct r
<action>The only valid terminal states for a repository-changing run are: delegated delivery completed, an explicit blocker, or an explicit policy pause awaiting user input.</action>
<action>Summarize behavior-level changes, not just file names.</action>
<action>Let the delegated delivery skill own pull request title/body derivation, screenshot and screencast embedding, related-PR links, and any PR metadata refresh using its shared `pr-metadata-update-recipe` block plus the relevant `pr-writing-guide` section instead of duplicating that procedure here.</action>
<action>Make clear what was completed, what evidence supports it, the scope actually covered, and any material item not verified or still pending. Keep those distinctions in natural prose rather than requiring fixed headings or boilerplate.</action>
<action>Keep the final completion report conversational and concise by default; do not turn routine successful execution into an audit log.</action>
<action>Do not add standalone `Validation`, `Checks`, or `Status` sections for routine successful runs.</action>
<action>Mention screenshot or screencast capture only when it materially affects the user's next step or the user explicitly asked about it.</action>
Expand Down
Loading