← All Sidekicks

FULCRUM CORTEX / SIDEKICK ROLE

Developer.
From a requirement to a reviewable change.

Investigate code, make a bounded change, run the relevant checks and verify an authorised release.

TRY A BRIEF LIKE THIS

“Fix the empty-name validation bug, keep the current design and show the passing focused checks.”

THE HANDOVER

Useful work.
A clear next decision.

A reviewable diff with behavioural validation and an accurate release status.

  • Find the cause of a reproducible bug.
  • Implement a small change with focused checks.
  • Track a release from source revision to live behaviour.

Where you stay in control

Work stays within the tools, accounts and actions you authorize. Sending, sharing, calling, publishing, purchases and production changes require the appropriate authorization. The public skill itself grants no access.

Plan a software task and follow its progress in the Fulcrum Code terminal.
Plan a software task and follow its progress in the Fulcrum Code terminal.

THE PUBLIC SKILL LIBRARY

Inside this Sidekick’s toolkit.

Make a reviewable code change

Investigate and implement a bounded software change in Fulcrum Code, preserving project conventions and validating the requested behaviour. Use for coding tasks in an existing project.

Example brief: “Fix the empty-name validation bug, keep the current design and show the passing focused checks.”

Expected handover: A reviewable diff with behavioural validation and an accurate release status.

Read the skill and its instructions ↗

Verify a release from source to live

Track and verify an authorised software release through source, checks, publication, deployment and live behaviour. Use when release completion or a disputed deployment status needs evidence.

Example brief: “Check whether the authorised release actually reached production and finish any recoverable prerequisite.”

Expected handover: A release record tied to the expected revision and live behaviour.

Read the skill and its instructions ↗

Read the product guide ↗

Skills provide instructions. Actual execution depends on configured integrations, permissions and the environment. A public skill does not itself grant access to private systems.

Put a developer Sidekick
to work with your team.

Bring your workflow. We’ll show the skills, access and human review it needs.