We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFNeed to check the working tree status of a Git repository.
THENUse the git_status tool from the Git MCP server. Pass the repository path as input to get the current status as text output.
IFNeed to view commit history with optional date filtering.
THENUse the git_log tool. Provide the repository path, optionally limit the number of commits (max_count) and filter by start/end timestamps. Timestamps accept ISO 8601, relative dates, or absolute dates.
IFNeed to create a new branch from an existing base.
THENUse the git_create_branch tool. Provide the repository path, a new branch name, and optionally a base branch name (defaults to current branch).
IFNeed to see changes in the working directory that are not yet staged.
THENUse the git_diff_unstaged tool. Provide the repository path and optionally specify the number of context lines (default 3).
IFNeed to unstage all currently staged changes.
THENUse the git_reset tool. Provide the repository path. It unstages all changes, leaving working directory untouched.
IFNeed to inspect the contents of a specific commit.
THENUse the git_show tool. Provide the repository path and a revision identifier (commit hash, branch name, or tag). Returns the full commit contents.
IFNeed to review changes that are staged and ready to commit.
THENUse the git_diff_staged tool. Provide the repository path and optionally the number of context lines.
IFNeed to stage specific files for the next commit.
THENUse the git_add tool. Provide the repository path and an array of file paths to stage. Confirms which files were staged.
IFNeed to commit staged changes with a descriptive message.
THENUse the git_commit tool. Provide the repository path and a commit message. The tool returns the new commit hash.
IFNeed to compare the current state with another branch or commit.
THENUse the git_diff tool with a target branch or commit hash. Optionally set context_lines for the diff output.
IFNeed to list branches in the repository with optional filtering.
THENUse the git_branch tool. Provide the repository path, specify branch_type (local, remote, or all), and optionally a commit sha that branches must contain or not contain.
IFNeed to switch to an existing branch.
THENUse the git_checkout tool. Provide the repository path and the target branch name. Confirms the branch switch.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site