Skip to content

feat: add minion config#300

Open
ninja-shreyash wants to merge 1 commit intomainfrom
sv/add-minions
Open

feat: add minion config#300
ninja-shreyash wants to merge 1 commit intomainfrom
sv/add-minions

Conversation

@ninja-shreyash
Copy link
Copy Markdown
Contributor

@ninja-shreyash ninja-shreyash commented Mar 20, 2026

What is Minion?

Minion is a GitHub App that turns issues into merged PRs using Claude Code agents. It listens for webhook events, implements solutions autonomously, runs code review, and can auto-merge safe changes.

Configuration

Adds .minion.yml with the following setup:

  • Runtime: npm, Node 20
  • Validation: unit tests (vitest), linting (oxlint), build (rollup)
  • Autonomy: supervised — creates draft PRs requiring human review
  • Protected paths: auth core, CI workflows, CLI deploy commands
  • Context files: CLAUDE.md, README, CONTRIBUTING guide

Getting Started

  1. Create an issue — Write a clear, specific GitHub issue describing the task
  2. Add the minion label — This triggers the agent to pick up the issue
  3. Agent works — Minion reads the issue, explores the codebase, and implements a solution
  4. Draft PR created — Since we're in supervised mode, a draft PR is opened for review
  5. AI code review runs — An autonomous review checks for correctness and safety
  6. Human merges — Review the PR and merge when satisfied

As confidence grows, autonomy can be graduated: supervisedassistedautonomous.

@sonarqubecloud
Copy link
Copy Markdown

Comment thread .minion.yml
Comment on lines +5 to +8
validation:
test_command: "npm test"
lint_command: "npm run lint"
build_command: "npm run build"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we also add docs and typecheck for the validation

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can extend later.. I have not yet explored the entire config template (it has a lot of other features).

But in order to test/evaluate for our use case, we need to merge this first (since it needs to be present in default branch to run).. and once we get to a point that it completes our implementation loop, then we can tweak the configs.

This is the bare minimum config present in minion repo Readme

Comment thread .minion.yml
autonomy: supervised

model:
implementer: opus
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

opus is the most capable but also the most expensive. Would sonnet not give good results?
which account would be used for this?

Copy link
Copy Markdown
Contributor Author

@ninja-shreyash ninja-shreyash Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sonnet wont give very good results. maybe default is good. It is using a central minion account, and the token is also central present in minion repo

Comment thread .minion.yml
protected_paths:
- "src/core/auth/**"
- ".github/workflows/**"
- "packages/cli/src/commands/deploy/**"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why just the deploy file? Why not the whole packages folder?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

anyways we are using supervised mode for now. This would come handy when we switch to autonomous mode which we are not going to do atleast in near future

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.

2 participants