agentleFS
projectbluefinprojectbluefin/finpilot/AGENTS.md

finpilot

AGENTS.md131 starsChanged 18 days agoApache-2.0View on GitHub

Working notes for agents in this repository. overview maps how the image is assembled and says which skill covers what; the procedures live under .agents/skills/. These hold for every change: - Conventional Commits — <type>[scope]: <description>. - Validate before committing. just lint shellchecks every tracked shell script, just check verifies Justfile syntax, and just test-unit runs the suite. just validate-brewfiles and just validate-flatpaks cover those files. The validate status check runs shellcheck and hadolint on a pull request. - Confirm…

The file

Files
AGENTS.md

AGENTS.md

Working notes for agents in this repository. overview maps how the image is assembled and says which skill covers what; the procedures live under .agents/skills/.

Gates

These hold for every change:

  • Conventional Commits — <type>[scope]: <description>.
  • Validate before committing. just lint shellchecks every tracked shell script, just check verifies Justfile syntax, and just test-unit runs the suite. just validate-brewfiles and just validate-flatpaks cover those files. The validate status check runs shellcheck and hadolint on a pull request.
  • Confirm before pushing — show the diff and wait.

Branches and releases

main is the testing branch: pushes publish :stable-testing. stable is production, and it never rebuilds — execute-release.yml promotes the exact digest main already built. Promotion is main → stable through the auto-opened squash PR, and stable hotfixes sync back to main. stable takes no direct commits. The README owns the release table and the promotion gate's current limits.

Pull request comments

One comment per PR event; fold new findings into the existing one. Report what ran, whether it passed, and what blocked — nothing else. When the only finding is "tests pass", post nothing. Mention someone only to ask for a specific action, and do it inside the combined comment.

Attribution

End every commit with:

Assisted-by: <Model> via <Tool>

Self-improvement

Ship the work and update the owning skill in the same PR, not a follow-up. A skill is the home for durable learning; a changelog, a session note, or an "append here" section is not. When a workaround or convention surprised you, the next agent needs it.

Ownership

Humans triage and approve; agents work only on assigned or 3-clanker-queue issues. Keep changes to this repository: ublue-os/* is read-only. The shared lifecycle and labels are in projectbluefin/common's label workflow.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.