Skip to content

Latest commit

Β 

History

History
18 lines (15 loc) Β· 1.3 KB

File metadata and controls

18 lines (15 loc) Β· 1.3 KB

fledge

fledge exists so that the boring middle of software work β€” start it, run it, check it, review it, ship it β€” is the same small set of commands in every repository you touch, whatever language is inside. It should be useful the second you cd into an existing project, with nothing configured and nothing to learn, and it should get more useful, not more brittle, as you write your project's habits down. Anything that assumes one ecosystem belongs outside the core, so the tool you install stays small and the parts you opt into are yours to choose. Every guardrail it has β€” the refused push, the shown-before-run setup command, the untrusted plugin β€” is there because the alternative is discovering the problem after the damage. And because half the people using it now are agents, everything a person can read, a machine can parse.

Features

  • agent: AGENT (17 criteria)
  • ai: AI (17 criteria)
  • lane: LANE (24 criteria)
  • plugin: PLUGIN (25 criteria)
  • review: REVIEW (17 criteria)
  • run: RUN (17 criteria)
  • scaffold: SCAFFOLD (17 criteria)
  • setup: SETUP (21 criteria)
  • ship: SHIP (29 criteria)
  • spec: SPEC (13 criteria)