Skip to content

Agent: # DEV TASK PROMPT (FLOE) ## Project context Repo: malon64/f#209

Closed
malon64 wants to merge 1 commit intomainfrom
agent/po-floe-20260306-1154-T1
Closed

Agent: # DEV TASK PROMPT (FLOE) ## Project context Repo: malon64/f#209
malon64 wants to merge 1 commit intomainfrom
agent/po-floe-20260306-1154-T1

Conversation

@malon64
Copy link
Owner

@malon64 malon64 commented Mar 6, 2026

Automated changes by agent.\n\nInstruction:\n# DEV TASK PROMPT (FLOE)

Project context

Repo: malon64/floe
Language: Rust (main), plus orchestrator packages in Python.
Goal: produce clean, idiomatic, performant code consistent with existing architecture.

Task

Objective

Create docs/local-dev.md for Rust/Cargo local development that enables a first-time contributor to run Floe locally.

Scope (where to change)

  • docs/local-dev.md (new file only)

Non-goals (what NOT to touch)

  • Do not edit README.md in this task.
  • Do not change Rust application logic/code paths.
  • Do not modify CI/workflow configuration.

Implementation notes / constraints

  • Add sections: Prerequisites, Setup, Run, Test, Quality checks, Troubleshooting.
  • Commands should be copy-paste ready and aligned with this repo’s workspace:
    • cargo build
    • cargo run -p floe-cli -- --help
    • cargo run -p floe-cli -- run -c example/config.yml
    • cargo run -p floe-cli -- validate -c example/config.yml
    • cargo test
    • cargo fmt -- --check (or cargo fmt fallback if needed)
    • cargo clippy --workspace --all-targets -- -D warnings
  • Keep guidance concise and beginner-friendly.
  • Troubleshooting must include at least 3 actionable items.
  • Ensure all paths/commands are consistent with current repository layout.

Tests (mandatory)

What to add/update

  • Unit tests: put them under crates/floe-core/tests/unit/** (or the relevant crate’s tests dir).

  • Integration tests (only if needed for the change): crates/floe-core/tests/integration/**.

  • Docs-only task: no new Rust test files required.

  • Validate command snippets for syntactic correctness and repository consistency.

Local self-validation (must run before finishing)

Run and fix until green:

  • cargo fmt
  • cargo clippy --workspace --all-targets -- -D warnings
  • Rust tests: run the relevant filtered suite(s) for changed modules (avoid full suite unless necessary)
  • If Python orchestrators touched: run the relevant pytest path(s) only

Git / PR requirements (mandatory)

  • Start from main (worktree branch created from origin/main).
  • Make focused commits.
  • Ensure changes are staged: git add -A
  • Commit with a clear message.
  • Push branch to origin.
  • Ensure a PR can be created (there must be at least one commit).

Acceptance criteria

  • docs/local-dev.md exists and documents complete local Rust workflow.
  • Includes the required sections (Prerequisites, Setup, Run, Test, Quality checks, Troubleshooting).
  • Commands are accurate for this repository and runnable by a first-time contributor.
  • Troubleshooting includes at least 3 practical fixes.
  • At least one commit exists on the task branch so PR creation succeeds.

Output requirement

When done, provide:

  • Summary of changes
  • Commands run + results
  • What tests were added/updated and where

## Project context
Repo: malon64/f
@malon64 malon64 closed this Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant