task-to-agent
Claude Code skill: hand an issue or PR task to a coding agent in a Paradev workspace, then verify and open the PR
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/chaoperties--task-to-agent)HTML
<a href="/listings/chaoperties--task-to-agent"><img src="/api/listings/chaoperties--task-to-agent/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Needs `git`, `gh` (logged in), `jq`, `perl`, Docker and the Paradev CLI (`superset`).
git clone https://github.com/chaoperties/task-to-agent.git && cd task-to-agent && ./install.sh
`install.sh` symlinks `skills/*` into `~/.claude/skills` and `~/.agents/skills`, so `git pull` updates the skill. It skips a real `task-to-agent` directory that is already there.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 75 lines
- <div align="center">
- # task-to-agent
- ### Hand the task to an agent. Keep the verification.
- [Install](#install) · [Use](#use) · [Profiles](#profiles) · [License](#license)
- [](https://docs.claude.com/en/docs/claude-code/skills)
- [](https://docs.paradev.com/cli/getting-started)
- [](https://github.com/chaoperties/task-to-agent/commits/main)
- [](LICENSE)
- <br>
- [](#install)
- </div>
- Claude Code skill `/task-to-agent`: hand an issue, or a task on an open PR (E2E, review fixes,
- follow-up), to a coding agent (Codex, Claude, Gemini, …) in its own [Paradev](https://paradev.dev)
- workspace, then verify the result and open the PR yourself.
- Flow: load repo profile → pick task → clarify decisions → branch + workspace + env + spec →
- dispatch agent → wait in a background shell → verify (rerun checks yourself) → PR → clean up after merge.
- ## Install
- Needs `git`, `gh` (logged in), `jq`, `perl`, Docker and the Paradev CLI (`superset`).
- ```bash
- git clone https://github.com/chaoperties/task-to-agent.git && cd task-to-agent && ./install.sh
- ```
- `install.sh` symlinks `skills/*` into `~/.claude/skills` and `~/.agents/skills`, so `git pull`
- updates the skill. It skips a real `task-to-agent` directory that is already there.
- ## Use
- In a repo that has a profile:
- ```
- /task-to-agent # pick the next ready issue
- /task-to-agent 42 codex # issue or PR #42, Codex worker
- ```
- or say "ส่งงานให้ codex", "หา issue ถัดไป", "ให้ codex ทำ e2e PR 42".
- ## What's inside
- | Path | Purpose |
- |------|---------|
- | `skills/task-to-agent/SKILL.md` | The workflow, the same for every repo |
- | `skills/task-to-agent/profiles/<repo>.md` | Your profiles (git-ignored): branches, env, ports, checks, PR body, review checklist |
- | `skills/task-to-agent/profiles/_template.md` | Keys a new profile must fill |
- | `skills/task-to-agent/spec-template.md` | Spec template used when a profile has no repo copy |
- ## Profiles
- The repo ships no profiles, only `_template.md`. Run `/task-to-agent` in your project: with no
- matching profile the agent drafts `profiles/<repo>.md` from the project's AGENTS.md, compose file
- and CI and asks you to confirm it.
- Profiles are git-ignored, so they stay on your machine and `git pull` never touches them. Keep
- absolute paths, Paradev project ids and logins out of them (the skill looks those up), and a
- profile can be handed to a teammate as is.
- ## Changing the skill
- `SKILL.md` wording changes how agents behave. In the PR, describe what the agent did wrong before
- and the run where you checked it now behaves right.
- ## License
- MIT, see [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.