do

Automate software delivery tasks from research through PR and CI to shipping.

Updated Apr 26, 2026

Search Tags:#automation #git #workflow #devops #deployment #ci #pull-request

Ready to run

npx skills add https://github.com/juspay/ci --skill do-juspay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do
Source: https://github.com/juspay/ci/tree/main/.claude/skills/do
Command: npx skills add https://github.com/juspay/ci --skill do-juspay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Do automates end-to-end software tasks from research through PR and CI to shipping, reducing manual coordination and decision latency.

Core Features & Use Cases

End-to-end automation: research, implement, test, PR, and ship within a unified workflow.
Configurable flow: supports --no-git to operate without creating branches or PRs; supports --from to start at a specific step; supports --review to pause for user planning.
Forge-aware results tracking: uses scripts/do-results to record step status and forges (github/bitbucket/unknown) and generates a consistent 14-step UI progress trail.

Quick Start

Provide a task description and the Do skill will autonomously execute the full cycle from planning to deployment.

Frequently Asked Questions about do

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate the software delivery workflow from a GitHub issue to a merged pull request?▼

To automate software delivery from a GitHub issue to a pull request, provide a task description with YAML frontmatter specifying name and description. The system autonomously executes research, implementation, testing, and PR creation in a structured workflow.

Can I run code changes locally without creating a git branch or pull request?▼

Yes, you can apply changes in-place without creating a git branch or pull request by using the --no-git option. This modifies your working directory directly while still tracking step status through the results script.

Does the automated deployment workflow support both GitHub and Bitbucket repositories?▼

Yes, the automated deployment workflow supports both GitHub and Bitbucket through forge-detection. It identifies the forge type and conditionally applies the correct pull request creation steps based on whether the repository is on GitHub, Bitbucket, or an unknown platform.

What dependencies do I need to run end-to-end DevOps task automation?▼

You need the command-line JSON processor jq installed to run end-to-end DevOps task automation. This dependency is required for the scripts to parse data and record the 14-step progress trail during the software delivery cycle.

How do I resume a CI workflow from a specific step without repeating earlier actions?▼

You can resume a CI workflow from a specific step without repeating earlier actions by using the --from option to start at a designated point. The --review-model option can also pause execution for user planning before proceeding.

What is the best way to track progress during automated pull request creation?▼

The best way to track progress during automated pull request creation is using the integrated results script. It records step status and forge type, generating a consistent 14-step UI progress trail that visualizes the workflow from research to shipping.