Skip to content
Docs
Browse all documentation

Build · 9 min read

Coding workflow

Inspect, change, test, and explain a codebase with a reviewable evidence trail.

On this page
  1. Describe the outcome
  2. Inspect before editing
  3. Make scoped edits
  4. Verify in proportion to risk
  5. Read the final handoff

Describe the outcome

State the bug or feature in observable terms. Include platform, reproduction, expected behavior, constraints, and verification. Ask for diagnosis when you do not want edits; ask to fix or implement when changes are authorized.

The rollback tray is hidden behind the composer at this window size.
Keep the collapsed summary visible, improve the restore icon,
and keep expanded items scrollable. Verify UI tests and a desktop screenshot.

Define the state, defect, intended behavior, and verification.

Inspect before editing

Gyroscape searches the repository, reads relevant instructions, follows data flow, and checks existing changes before implementing. Small work can be direct; broad work gets a proportionate plan without an arbitrary file limit.

Clarification is needed only when a missing choice materially changes the result. Otherwise Gyroscape makes a bounded assumption and continues.

Make scoped edits

Tools can read and search files, apply patches, and run project commands. Gyroscape preserves unrelated user changes and avoids destructive source-control commands unless clearly requested.

UI changes use existing components, icons, spacing, and themes. Backend changes preserve public mappings, billing, and compatibility unless explicitly changed.

Verify in proportion to risk

Run focused tests and type checks for logic changes. Render UI changes at the affected size. Use documented build commands and separate environment failures from code failures.

Useful evidence

  • Exact focused tests that passed.
  • Type-check, lint, or build status.
  • A screenshot for visual changes.
  • Any limitation not tested locally.

Read the final handoff

The final response leads with the result, identifies important files or behavior, states verification, and discloses real caveats. Open Changes for line-by-line confirmation.

Related articles

Models and reasoning effortChoose a Gyroscape model and effort level that fits the task, latency, and usage.Terminal and coding toolsUnderstand file tools, patches, commands, interactive terminals, and background processes.Review changes, roll back, and restoreInspect the diff, roll back to an earlier message, and restore work from the composer tray.