agentic-platform

Plugin agentic-platform from marketplace danievanzyl in danievanzyl/code-skills. Commands read from the repo's manifest — 10 days ago.

Skills (46)

• afk-issue-herdr

  Herdr-native sibling of afk-issue — implements ONE GitHub issue end-to-end by running the afk-task-runner then the code-reviewer, each as a full Claude Code session inside its own herdr pane (not an in-process subagent), opening a reviewed PR. Use when the user says "afk issue #N in herdr", "run iss

• afk-issue

  Implement ONE GitHub issue end-to-end with the afk-task-runner, then the code-reviewer, opening a PR (default base main, override with a branch). Orchestration glue for a single targeted issue — use when the user says "afk issue #N", "implement #N and review it", "run the afk runner on issue N", "bu

• apple-design

  Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking,

• archify

  Create validated architecture, workflow, sequence, data-flow, lifecycle/state, ERD, class, tree, timeline, and waterfall diagrams as explorable standalone HTML with dark/light themes, motion and image/SVG/WebM export. Accept requirements or Mermaid; inspect repository evidence for code-backed diagra

• ask-matt

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• feature-branch-fan-in-herdr

  Herdr-native sibling of feature-branch-fan-in — drives a sequential queue of ready-for-agent GitHub issues, each through the full afk-issue-herdr pipeline (orchestrator → runner → reviewer, each a herdr pane agent) targeting a feature/integration branch, squash-merging each into the feature branch b

• feature-branch-fan-in

  Drives a feature-branch fan-in — implements a set of ready-for-agent GitHub issues whose design is already locked by spawning the afk-task-runner per issue (each PR targeting a feature/integration branch, NOT main), then the code-reviewer on each PR, squash-merging each into the feature branch, and

• frontend-design

  Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

• gh-draft-pr

  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

• gh-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.

• grill-me

  A relentless interview to sharpen a plan or design.

• grill-with-docs

  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff-herdr

  Herdr-native sibling of handoff — produces a Handoff document, then routes it to a repo-matched waiting pane agent (idle/blocked) instead of leaving placement to the human, spawning a clean target when none waits. Serves both Offload (my own context is too large, hand off and stop) and Dispatch (rou

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• implement-spec

  Implement the result of /to-spec and /to-tickets in code.

• implement

  Implement a piece of work based on a spec or set of tickets.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• install-anti-slop

  Install, configure, update, or upgrade vendored anti-slop Oxlint plugins. Use when adding anti-slop, picking up upstream rules or fixes, or migrating an existing installation while preserving local customizations.

• jira-acli

  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", "st

• jira-update

  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 fo

• obsidian-vault-manager

  ALWAYS use this skill when the user mentions Obsidian, their vault, or the `obsidian` CLI — even in passing. This skill manages notes, tasks, architecture decisions, and project context in the user's Obsidian vault via the `obsidian` CLI tool. Also trigger when the user asks to create meeting notes,

• pr

  Use when writing a PR body.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• ralph-commit

  Make a git commit whose message captures key decisions, files changed, and blockers/notes for the next iteration. Use when the user says "/ralph-commit", "checkpoint commit", "iteration commit", "commit with decisions", or wants to record an iteration's state in git before moving on (e.g. inside a r

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• retro

  Conduct a retrospective on a coding session.

• review

  Render review context for the current branch and dispatch the code-reviewer subagent. Usage `/review <issue-number> "<issue-title>"`.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• teach

  Teach the user a new skill or concept, within this workspace.

• tf-remote-state-outputs

  Extract all Terraform outputs from a repo and generate a REMOTE_STATE_OUTPUTS.md documenting them for consumers who reference this project via terraform_remote_state. Use when setting up a new Terraform project, after adding/removing outputs, or when you need a quick inventory of what a project expo

• tf-style-guide

  Terraform style conventions, formatting standards, and best practices for writing clean HCL. Use when users ask about Terraform coding standards, file organization, naming conventions, formatting rules, variable/output structure, or when writing new Terraform configurations. Also use when reviewing

• to-questionnaire

  Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• update-docs-ai-diagrams

  Update Mermaid diagrams in documentation to reflect recent codebase changes.

• wait-what

  Stop. That last message did not land: re-pitch it.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• wrap-up

  Post-merge wrap-up: confirm a PR is merged, update local main, close the worktree + branch, then offer to write a handoff doc for the next session. Use when the user says "this is merged", "merge and clean up", "merged, clean up", "update main and clean up", "wrap up", "done with this PR", or "this

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Subagents (11)

• afk-task-runner

  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.

• code-reviewer

  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 P

• codebase-analyzer

  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! :)

• codebase-locator

  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

  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 locatio

• gh-search-researcher

  Need to research GitHub repos, PRs, issues, discussions, code, or users? The gh-search-researcher uses the gh CLI exclusively to find information across GitHub. Great for finding issues, understanding PR history, searching code on GitHub, exploring repo activity, and investigating GitHub-hosted proj

• hello-world

  Minimal test agent for observing subagent behaviour. Use when the user wants to test agent invocation, tool access, or return-value handling — e.g. "run the hello-world agent", "test agent behaviour".

• swift-expert

  Expert Swift developer specializing in Swift 6.2+ with async/await, SwiftUI, and protocol-oriented programming. Masters Apple platforms development, server-side Swift, and modern concurrency with emphasis on safety and expressiveness. Use when developing iOS/macOS applications with Swift.

• thoughts-analyzer

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

• thoughts-locator

  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

• web-search-researcher

  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

Hooks (7)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/guard-sensitive-files.sh

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/hooks/afk-handoff.sh

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/hooks/capture-run.sh

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/hooks/code-reviewer-push.sh

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/hooks/capture-run.sh --role reviewer

• SubagentStop

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-evaluator.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/capture-run.sh

Similar plugins