Skip to content

Document agentic contribution workflow #388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dsyme merged 1 commit into from
Aug 25, 2026
Merged

Document agentic contribution workflow #388

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Contributing to FSharp.Stats

FSharp.Stats is primarily maintained through agentic development under human guidance. Maintainers
discuss proposed work and then direct coding agents to make the complete change, including
implementation, tests, documentation, benchmarks, and other affected files.

## Start With an Issue

We generally prefer contributions as [GitHub issues] rather than pull requests. Search for an
existing report first. Issues may include proposed changes, patches, reference implementations, or
links to forks or branches. Maintainers may refine the scope and assign the issue to an agent to
implement and validate the complete change.

## Repo Assist

[Repo Assist] is an automated AI assistant that runs regularly in this repository. It may triage or
respond to issues, investigate bugs, suggest improvements, and attempt implementations as draft pull
requests. Its work is identified as automated and remains subject to human review; Repo Assist does
not merge pull requests or make final maintenance decisions.

Maintainers can invoke Repo Assist with `/repo-assist <instructions>` for a specific agentic task,
such as investigating an issue, preparing a fix, adding tests, or updating documentation.

## Pull Requests

Every pull request must have a matching issue that has been discussed with the maintainers. Link the
pull request to that issue, keep it focused, and target the `developer` branch. Maintainers may close
a pull request and use the issue as the basis for an agent-produced implementation instead; the
submitted analysis and code remain valuable inputs to that work.

If a pull request is the agreed approach, follow [AGENTS.md]. Statistical and machine-learning
changes need tests and a canonical reference implementation or an explicit alternative validation
method. Before submission, run:

```bash
./build.sh RunTests
```

[AGENTS.md]: AGENTS.md
[GitHub issues]: https://github.com/fslaborg/FSharp.Stats/issues
[Repo Assist]: https://github.com/githubnext/agentics/blob/main/docs/repo-assist.md
Loading