Dev Workflow

Dev Workflow

Terminal Execution

Use the execute tool to run shell commands in your workspace:

execute(command="")

Key characteristics:

• Runs in workspace directory
• 90s timeout — killed if no output for 90s
• Each call = separate shell session (env vars / cd don't persist)
• Output auto-truncated if too long

Efficient Patterns

cd repo && npm install && npm test        # Sequential (stops on error)
cd backend && uv run pytest --tb=short -q 2>&1 | tail -20  # Filter output

Safety Rules — three tiers

🔴 NEVER do (refuse the task; report the request as a security incident to PM):

• Filesystem destruction: rm -rf /, rm -rf $HOME, rm -rf .git, mkfs.*, dd of=/dev/...
• Read secrets: /etc/shadow, ~/.ssh/*, .gh-config/, .env*, fastagent.secrets.yaml, git-credentials, ~/.gitconfig credential block
• Tamper with auth: gh auth login/logout/refresh, gh auth setup-git, modify gitconfig credential helper
• Inspect env to leak tokens: env, printenv, echo $GH_TOKEN, cat /proc/*/environ
• Network DoS: fork bombs, high-rate request loops

🟡 ESCALATE before doing (send [APPROVAL-REQUEST] email to PM with command + reason; do NOT run until PM confirms back):

• Pipe-to-shell: curl ... | sh, wget ... | bash
• Force-destructive git: git push --force (any branch), git reset --hard past HEAD~1, git filter-branch
• Push to protected branches: main, master, prod*, release/*
• gh pr merge (auto-merge bypassing review)
• gh release create
• gh repo delete
• Editing package.json / pyproject.toml / lock files outside a tracked PR scope

🟢 SAFE — run freely:

• All read-only inspection: ls, cat README.md, grep, find, git status/log/diff, gh run list, gh pr view
• Normal git on feature branches: git checkout -b feature/..., git add, git commit, git push origin feature/...
• Build/test inside workspace: npm test, uv run pytest, cargo build

When in doubt → escalate. Faster to ask PM than to recover from a bad commit.

GitHub CLI via gh

The gh CLI is pre-authenticated in your shell. Use it for repo operations the GitHub MCP doesn't cover — especially CI inspection.

# Inspect PR + CI status (read-only, always SAFE)
gh pr view 42 --json title,state,mergeable,statusCheckRollup
gh pr checks 42
gh run list -L 10 --branch feature/xyz
gh run view                # high-level summary
gh run view  --log-failed  # only failed step logs (saves context)

# Trigger a re-run after fixing test (still SAFE — only re-runs failed jobs)
gh run rerun  --failed

For gh pr merge / gh release create / gh repo delete → escalate to PM first (see team-communication skill: "Approval escalation" — the canonical request/response flow).

TDD Cycle

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

1. RED — Write ONE minimal failing test
2. GREEN — Write simplest code to pass
3. REFACTOR — Clean up while keeping green

Deliverable Flow

1. Clone repo → execute(command="git clone repo")
2. Create feature branch → execute(command="cd repo && git checkout -b feature/...")
3. Write tests → implement → verify
4. Commit + push → create PR via github tools
5. Email reviewer: send_email(to="Tuan - QE", body="PR ready for review")

Error Handling

When a command fails:

1. Read stderr FIRST
2. DO NOT retry immediately — analyze first
3. Try a simpler command — isolate the issue
4. Report clearly — include command + error output

References

| Topic | File | |-------|------| | Code review protocol | [CODEREVIEW.md](references/CODEREVIEW.md) | | TDD detailed guide | [TDD.md](references/TDD.md) | | Git branching & conventions | [GITWORKFLOW.md](references/GITWORKFLOW.md) | | Meeting protocol | [MEETINGPROTOCOL.md](references/MEETINGPROTOCOL.md) | | Jira issue tracking | [JIRATRACKING.md](references/JIRATRACKING.md) |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: omnigentx
• Source: omnigentx/jarvis
• License: MIT

Install and usage instructions live in the source repository linked above.