[lgcsu]

Add a local agent workflow for picking and solving issues in this fork.

MCP server (mcp_server/, .mcp.json):

• algodev server exposes run_doctests and ruff_check for one .py file
• runs in the algodev-mcp image with no network and the repo mounted read-only; doctests use free-threaded python3.15t
• image bakes in git, pre-commit and the hook environments from .pre-commit-config.yaml; precommit-check runs the suite on a scratch copy of the repo and prints any fixes as a diff
• check_server.sh rebuilds the image and smoke-tests the server

Hooks (.claude/hooks/, .claude/settings.json):

• issue_picker / issue_context: list and select upstream issues, save the selection to .claude/issue.md and show it at session start
• protect_files: block edits CONTRIBUTING.md rules out (README.md, DIRECTORY.md, uv.lock, notebooks, new directories)
• guard_master: no commits or pushes on master
• check_py: ruff and doctests after each edit of a .py file
• verify_on_stop / commit_gate: run verify.sh (ruff check, ruff format, doctests, filename check, pre-commit) on changed or staged .py files

Skill (.claude/skills/solve-issue/):

• checklist for reviewing an issue fix against CONTRIBUTING.md

Describe your change

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Add or change doctests? -- Note: Please avoid changing both code and tests in a single pull request.
• Documentation change?

Checklist

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that pull requests will not be merged if they fail the automated tests.
• This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• All new Python files are placed inside an existing directory.
• All filenames are in all lowercase characters with no spaces or dashes.
• All functions and variable names follow Python naming conventions.
• All function parameters and return values are annotated with Python type hints.
• All functions have doctests that pass the automated testing.
• All new algorithms include at least one URL that points to Wikipedia or another similar explanation.
• If this pull request resolves one or more open issues, then the description above includes the issue number(s) with a closing keyword: "Fixes #ISSUE-NUMBER".

[algorithms-keeper]

Closing this pull request as invalid

@lgcsu, this pull request is being closed as none of the checkboxes have been marked. It is important that you go through the checklist and mark the ones relevant to this pull request. Please read the Contributing guidelines.

If you're facing any problem on how to mark a checkbox, please read the following instructions:

• Read a point one at a time and think if it is relevant to the pull request or not.
• If it is, then mark it by putting a x between the square bracket like so: [x]

NOTE: Only [x] is supported so if you have put any other letter or symbol between the brackets, that will be marked as invalid. If that is the case then please open a new pull request with the appropriate changes.

[lgcsu]

Apologies! This was a misplaced target branch for pr with some wip educational code.