agentic-platform

Resume work from handoff document with context analysis and validation

Validate implementation against plan, verify success criteria, identify issues

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

Autonomous AFK task runner. Selects the next open issue from issues or gh issue, implements it using TDD, runs feedback loops, commits, and files the issue. Use when the user asks to "work through the AFK queue", "pick up the next AFK task", or invokes this agent explicitly. Skips HITL issues.

Reviews code changes on the current branch for clarity, edge cases, and bugs. Writes tests, fixes issues found, commits with "RALPH: Review -" prefix. Use proactively after the AFK runner completes a task, or when explicitly asked to review the current branch. The invoking message must include the branch name, issue number, and issue title.

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!

Commit any outstanding changes, push the current branch, and open a draft PR via the gh CLI. Use this skill whenever the user says "/gh-draft-pr", "open a draft PR", "ship a draft", "raise a draft PR", "push and open a PR", or otherwise wants to take their local branch from working state to a draft PR on GitHub in one step. Also trigger when the user mentions draft PRs, opening a PR for review-not-yet-ready work, or wants their WIP up on GitHub.

Use the gh CLI to interact with GitHub when the user references GitHub URLs, repos, PRs, issues, actions, releases, or any github.com resource. Activates for GitHub URLs (github.com/*), PR/issue references (#123), repo references (owner/repo), or questions about GitHub resources.

Manage git worktrees with a consistent repo layout: <repo>/src (main checkout) + <repo>/<branch> (worktrees). Use this skill whenever the user wants to: start a new feature ("new feature X", "start feature X"), close/clean up a worktree after a PR is merged ("close worktree", "clean up branch X", "worktree done"), clone a repo for worktree-based development, add a new worktree/branch, list worktrees, or asks about their worktree setup. Also trigger on: "set up repo", "clone for worktrees", "new worktree", "add branch", "remove worktree", "worktree list", "create_worktree", or any mention of the <repo>/src layout convention.

Manage Jira tickets via the acli CLI. Use this skill whenever the user mentions Jira tickets, ticket status, sprint work, CPE tickets, or wants to interact with their Jira board — even if they don't say "Jira" explicitly. Triggers on: ticket references (CPE-1234), status changes ("move to done", "start working on"), listing assigned work, creating tickets or sub-tasks, linking PRs to tickets, or summarising PR changes for Jira. Also activate when the user says "my tickets", "what am I working on", "create a ticket", "update the ticket", or references a board/sprint.

Post a concise development update to a Jira ticket summarising committed changes vs main, with optional status transition. Use this skill whenever the user says "/jira-update", "update the ticket with changes", "post changes to Jira", or wants to sync their git work back to a Jira ticket. Trigger format: /jira-update <ticket> [done|in progress|blocked]. If only a ticket is given, posts a summary comment. If a status is also given, transitions the ticket after commenting.

4 hooks across 3 events