humanlayer

Create git commits for session changes with clear, atomic messages

Generate comprehensive PR descriptions following repository templates

Create git commits with user approval and no Claude attribution

Create handoff document for transferring work to another session

Create detailed implementation plans through interactive research and iteration

Create detailed implementation plans with thorough research and iteration

Create implementation plans with thorough research (no thoughts directory)

---

Debug issues by investigating logs, database state, and git history

Generate comprehensive PR descriptions following repository templates

Generate comprehensive PR descriptions following repository templates

Create Linear ticket and PR for experimental features after implementation

Implement technical plans from thoughts/shared/plans with verification

Iterate on existing implementation plans with thorough research and updates

Iterate on existing implementation plans with thorough research and updates

Manage Linear tickets - create, update, comment, and follow workflow patterns

Set up worktree for reviewing colleague's branch

Research ticket and launch planning session

Execute ralph plan and implementation for a ticket

Implement highest priority small Linear ticket with worktree setup

Create implementation plan for highest priority Linear ticket ready for spec

Research highest priority Linear ticket needing investigation

Document codebase as-is with thoughts directory for historical context

Research codebase comprehensively using parallel sub-agents

Document codebase as-is without evaluation or recommendations

Resume work from handoff document with context analysis and validation

Validate implementation against plan, verify success criteria, identify issues

Discovers relevant documents in thoughts/ directory (We use this for all sorts of metadata storage!). This is really only relevant/needed when you're in a reseaching mood and need to figure out if we have random thoughts written down that are relevant to your current research task. Based on the name, I imagine you can guess this is the `thoughts` equivilent of `codebase-locator`

The research equivalent of codebase-analyzer. Use this subagent_type when wanting to deep dive on a research topic. Not commonly needed otherwise.

Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)

Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.

codebase-pattern-finder is a useful subagent_type for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!

Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagent_type today to find any and all answers to your questions! It will research deeply to figure out and attempt to answer your questions! If you aren't immediately satisfied you can get your money back! (Not really - but you can re-run web-search-researcher with an altered prompt in the event you're not satisfied the first time)

Creates a new git/jj worktree for development work with proper setup, dependencies, and optional thoughts initialization. Use when user needs to create a new worktree for feature development or bug fixes.

Generates metadata for research documents and specifications including date/time, git commit, branch, and repository info. Use when creating research documents, handoffs, or any documentation that needs timestamp and git metadata.