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

Automatic type-check and build after code changes #6154

New Issue
Open
opened 2026-02-16 18:01:06 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:01:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @mohammedevan09 on GitHub (Jan 15, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Feature Request: Automatic Type Check and Build After Code Changes

Description

After completing a code change, the tool should automatically run type-checking and build checks.

Right now, I have to manually prompt it every time to:

  • Run the type checker
  • Run the build

This is easy to forget and breaks the workflow.

Other tools like Cursor and Antigravity already do this automatically after code changes, which makes development much smoother and safer.

Expected Behavior

  • Automatically run type-checking after code modifications
  • Automatically run build checks after code modifications
  • Report errors immediately without requiring a manual prompt

Why This Matters

  • Saves time
  • Prevents shipping broken builds
  • Improves developer experience
  • Matches the behavior of competing tools (Cursor, Antigravity)
Originally created by @mohammedevan09 on GitHub (Jan 15, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ## Feature Request: Automatic Type Check and Build After Code Changes ### Description After completing a code change, the tool should automatically run **type-checking** and **build checks**. Right now, I have to manually prompt it every time to: - Run the type checker - Run the build This is easy to forget and breaks the workflow. Other tools like **Cursor** and **Antigravity** already do this automatically after code changes, which makes development much smoother and safer. --- ### Expected Behavior - Automatically run type-checking after code modifications - Automatically run build checks after code modifications - Report errors immediately without requiring a manual prompt --- ### Why This Matters - Saves time - Prevents shipping broken builds - Improves developer experience - Matches the behavior of competing tools (Cursor, Antigravity)
yindo added the discussion label 2026-02-16 18:01:06 -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 discussion
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#6154
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?