Skip to content
Agentmart
Submit a tool

dev-loop

Start the Jira-to-PR developer loop for a ticket.

Skill by sardul3

IndexedMIT
Write a review

Chalk Labs

Need help deploying dev-loop?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/sardul3-dev-loop

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Start the Jira-to-PR developer loop for a ticket. Use when the user says /dev-loop, work this Jira story, or run the conductor from a repo under ~/dev.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/dev-loop

What's inside

Skill name
dev-loop
Description
Start the Jira-to-PR developer loop for a ticket. Use when the user says /dev-loop, work this Jira story, or run the conductor from a repo under ~/dev.
License
MIT
Instructions
33 lines in SKILL.md · view on GitHub

Before installing

  • Instructions call the network
  • Instructions read files in your home folder (~/.ssh, ~/.aws…)

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Dev-loop

Run the conductor. Do not use Jira MCP or GitHub MCP. Knobs live in `~/.config/dev-conductor/dev-loop/config.yaml`. Real Jira needs `ATLASSIAN_BASE_URL`, `ATLASSIAN_EMAIL`, `ATLASSIAN_API_TOKEN` in `~/.config/dev-conductor/secrets.env`.

## Repo (do not guess)

If the user did not pass `--repo` and the current directory is not a git repo under `~/dev`:

1. Run `python3 ~/.claude/hooks/dev-loop/cli.py repos --format json` and read the JSON.
2. **Ask the user with a dropdown** (Cursor: AskQuestion). Options: every `candidates[].label` (id = `path`) plus one extra option id `__create__` labeled with `create_label`.
3. Never pick a folder unless the user selected it.
4. If they choose `__create__`, ask for a folder name, then:
   `python3 ~/.claude/hooks/dev-loop/cli.py init-repo NAME`
   Use the printed path as `--repo`.
5. If they choose a `folder` (not `git`), `init-repo` that name or `start` will git-init it. Prefer `init-repo` so GitHub remote is created.
6. Then:
   `python3 ~/.claude/hooks/dev-loop/cli.py start KEY --repo PATH`

If cwd is already the right git repo, `start KEY` without `--repo` is fine.

```bash
python3 ~/.claude/hooks/dev-loop/cli.py start KEY [--repo PATH]
python3 ~/.claude/hooks/dev-loop/cli.py continue KEY
```

Poller: `cli.py poll` / `install-poller`. Never commit `main`/`master`.
Agent reads use brief output (`cli.py` with no args, `keys`, `status`, `progress`). Picker JSON is `--format json`. New connector: `brief.Connector` + `fetch()`.

Long-run caps (`caps.max_launches` / `max_tokens` / `max_budget_usd` / `wall_sec`, 0 = off) stop further agent launches and write `STOPPED` in the run dir. Unattended still needs these set; they do not default on. Parallelism is `queue.max_active` (worktree/treehouse slots), not tmux fan-out.

Isolation: example config uses `git.isolation: worktree` (native git worktree under `.{repo}-worktrees/{KEY}`) and `queue.max_active: 3`. `treehouse` remains opt-in. Start from the clone under `~/dev`. A fourth in-progress ticket exits until one ships or you release its worktree/lease.

From sardul3/dev-conductor, MIT.

More from sardul3/dev-conductor

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 30, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from sardul3

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get dev-loop running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying dev-loop?

CallGet help
Cite this page

dev-loop skill. Agent Mart. https://agentmart.dev/skills/sardul3-dev-loop (last updated 2026-10-24)