Stay close to the code your AI is building.

Explore a clearer view of what changed, why it changed and what deserves your attention before you approve it.

Join the waitlist See the example

Understand the change before approving it

SITEKICK / THE POSSIBILITIES

A sidekick for software.

CONCEPT PREVIEW

Understand the change before approving it

See a proposed change explained through the files it touches, the behavior it alters and the assumptions behind it.

Trigger: a new diff or agent checkpoint.
Output: file-by-file summary, behavior example, uncertainty and source links.
Decision: approve, request changes or inspect a file.
Boundary: no implication that a natural-language summary replaces reviewing important code.
Follow-up: Refresh the explanation when the diff changes.

CONCEPT PREVIEW

Turn review feedback into an actionable next pass

Review comments should explain the issue and the next step. The concept prepares focused suggestions, relevant tests and documentation updates for your coding workflow.

Output: prioritized comments with file references, suggested test cases and proposed edits.
Human action: approve a draft change before any merge or release.
Show test states accurately: suggested, not run, passed or failed.
Trigger: New diff, review feedback or agent checkpoint
Follow-up: Refresh the explanation when the diff changes.

Turn review feedback into an actionable next pass — Illustrative example · Planned workflow

CONCEPT PREVIEW

See how the pieces fit together

Trace a request through the parts of the application it touches. Use a small architecture view to understand dependencies and ask better questions about a change.

Output: source-linked dependency diagram and affected components.
Follow-up: refresh explanation when the diff changes.
Boundary: diagrams describe inspected scope, not guaranteed complete system knowledge.
Trigger: New diff, review feedback or agent checkpoint
Decision: Inspect the source, approve a draft or request changes.

See how the pieces fit together — Illustrative example · Planned workflow

SITEKICK / EXAMPLE WALKTHROUGH

From shared context to your next choice.

A concept walkthrough—not a live product demonstration.

Walkthrough: Inspect sample diff → open changed-file map → review issue → ask for an explanation → approve a proposed revision in a concept UI.

Inputs: explicitly selected repository/diff, relevant docs and test output.

Sources and boundaries. Any released workflow must identify supported inputs, show source references and check times, surface missing information and failed checks, and let you inspect a proposed output before acting. These illustrations do not demonstrate a live integration.

You decide. No automatic buying, booking, payment, cancellation, merge or deployment is promised. Pause, notification and access controls must be documented with each release.

SITEKICK / CATEGORY FAQ