chaitin / chaitin/MonkeyCode

Feature Request: Post-Completion Change Summary After Task Execution

Open
#930 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4.7k
Forks
719
Avg merge
4h 30m
Merged PRs (30d)
83

Description

Summary

It would be helpful if MonkeyCode displayed a concise post-completion summary after every successful task. This would allow users to quickly understand the scope and impact of the generated changes without manually inspecting every modified file or Git diff.

Proposed Output

✅ Task Completed (12.4s)

📂 Files
• Created: 3
• Modified: 7
• Deleted: 1

📊 Code Changes
• +842 lines added
• -197 lines removed
• Net: +645

🧩 Components
• APIs created: 2
• Database migrations: 1
• Tests added: 14
• Documentation updated

🔍 Verification
✓ Build passed
✓ Lint passed
✓ Type check passed
✓ Tests: 48/48 passed

📦 Dependencies
• Added: express-rate-limit
• Updated: prisma
• Removed: moment

⚠️ Warnings
• 2 TODOs generated
• 1 file requires manual review

📝 AI Summary
Implemented JWT authentication, added refresh token support, updated middleware, created unit tests, and updated API routes.

Benefits

  • Quickly understand what the AI changed.
  • Improve transparency and trust in generated code.
  • Reduce the need to manually inspect every modified file.
  • Make large, multi-file agent workflows easier to review.
  • Provide a clear overview of validation results before committing changes.

This feature would significantly improve the developer experience by giving users an immediate, high-level overview of every completed task while keeping the interface clean and informative.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the task-completion flow and the existing sources for file changes, validation results, dependencies, and generated summaries. Define the summary data and presentation across successful tasks, then verify that it reports the requested categories accurately without disrupting the completion flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.