Open a pull request whose title says why the change matters and whose body opens with the problem in the requester's words. Use when asked to file, open, raise or create a PR, or to rewrite a PR's title or description.
Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.
Make a video, screen recording or demo clip play inline inside a GitHub Markdown file, pull request or release. Use when a video must play in the README or a PR, when asked to embed a video or add an inline player, or when a committed video renders blank.
Plan and carry out where an open-source repository gets listed so people find it, from GitHub itself to registries, directories, public catalogues, media, communities and funding. Use when asked to grow, promote or publicise a repo, or where else it could be listed.
Lay a decision out for the user so one word answers it, recommendation and pros and cons first, then how the thing works and what each choice changes. Use when the user says help-decide, asks for pros vs cons, or answers a question with "don't understand, explain".
Implements a requested change with the smallest complete diff, splitting genuinely independent work across parallel agents with non-overlapping file ownership, then integrates and verifies it. Use when invoked explicitly to build a feature or change.
Investigates a bug or unexpected behavior from reproduction to root cause with a panel of independent hypothesis agents, then fixes it only when the request asks for a fix. Use when invoked explicitly to debug, diagnose, or fix a reported failure.
Answers a question from the team's own record (chat archives, call transcripts, tickets, wiki pages, notes, any mix) through a knowledge-base adapter you fill in. Read-only, never from memory, every claim cited to the source it came from. Use when invoked explicitly to find what the team said or decided, who owns something, or whether a plan contradicts an earlier decision.
Reviews a pull request the way the team's reviewers do, grounded in reviewer learnings and past decisions captured in your knowledge base, verifies every finding against the code, and reports a severity-ranked review. Reports only; never posts, approves or merges without explicit instruction. Use when invoked explicitly on a PR, your own before requesting review or a teammate's.
Researches a question with independent parallel specialists that gather evidence from the code, its history, and primary sources, then synthesizes a ranked, cited answer. Use when invoked explicitly for research before a decision.
Audits a whole codebase in bounded waves of independent parallel auditors, publishes every verified finding ranked by severity, and applies only safe, in-scope repairs. Use when invoked explicitly for a codebase health review.
Review one or more pull requests as a single Workflow run (three lenses, one fixer, one adversarial verifier), comment the plan on each PR, push the fixes, then merge or close. Use when asked to review, fix up or merge a PR, or on "review-pr".
Bring cut-off work back exactly where it stopped after a usage limit, a crash, a restart or a compaction, without doing anything twice. Use when a session resumes after a limit or crash, when agents or background tasks died mid-work, or when asked to continue, resume or revive.
Runs a durable inspect/plan, implement, verify, and fresh-review loop toward an explicit repository goal, with optional lease-backed coordination across sessions. Use only when the user explicitly invokes sergio-loop.
Get an open-source repository listed in third-party awesome lists, one pull request per list, by each list's own rules. Use when asked to submit a repo to awesome lists or to continue an awesome-list sweep.
Draft a reply the user will send as themselves, with every factual claim checked against a live source first and posted only after they approve the exact text. Use when asked to answer a message, reply to a thread, PR or ticket comment, or check a reply the user wrote.
MCP server wrapping upstream mcp-atlassian with browser-cookie authentication via Playwright. Designed for Atlassian Server/Data Center instances behind corporate SSO where API tokens are not available. Authentication and serving are deliberately…
This project uses bd (beads) for issue tracking. Run bd prime for full workflow context. Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses…
Generated by LynxPrompt CLI This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands. Architecture in one line: issues live in a…
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.