Skip to content

feat(workshops/quality-engineering): add platform story coverage + delivery variants#123

Open
devin-ai-integration[bot] wants to merge 4 commits into
devin/1780546598-platform-story-coveragefrom
devin/1780845490-quality-engineering-platform-variants
Open

feat(workshops/quality-engineering): add platform story coverage + delivery variants#123
devin-ai-integration[bot] wants to merge 4 commits into
devin/1780546598-platform-story-coveragefrom
devin/1780845490-quality-engineering-platform-variants

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds platform delivery variants to the quality-engineering workshop, following the conventions in shared/WORKSHOP-VARIANTS.md.

Changes to README.md (cloud-agent baseline):

  • Adds a "Platform Context" section after Overview explaining this is the Cloud variant via app.devin.ai
  • Adds variant links at the top (README.platform.md, README.local.md)
  • Inserts cross-surface callout blocks in labs where natural (Desktop tips for PR review, CLI alternative for exploration, Agent Command Center for monitoring)
  • Adds a bullet in "Getting the Most from This Workshop" about the Agent Command Center

New README.platform.md (Desktop + Cloud variant):

  • Reframes the entire workshop for Devin Desktop as the primary interface
  • Replaces the 4-step web-app workflow with: explore locally → delegate to Cloud → monitor in Agent Command Center → one-click checkout PR review
  • References ACP, Spaces, multiple agents, and the local→cloud handoff pattern

New README.local.md (CLI / Devin Local variant):

  • Reframes for terminal-native workflow using devin CLI
  • Replaces cloud prompts with interactive CLI conversations and subagent parallelism
  • Adds "Cloud handoff" callouts for labs requiring autonomous execution (E2E with browser, long-running load tests, scheduled sessions)
  • All multi-clause implementation prompts use fenced code blocks per AGENTS.md rules

All three variants share identical lab structure (3 tracks, 9 labs, same repos and modules).

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/e4434f1d4a914181af8af57aea07d2f9
Requested by: @bsmitches


Open in Devin Review

…livery variants

- Update README.md (cloud-agent baseline) with Platform Context section,
  cross-surface callout blocks, and variant links
- Create README.platform.md for Desktop + Cloud delivery workflow
- Create README.local.md for CLI / Devin Local terminal-native workflow

All variants share the same lab structure (3 tracks, 9 labs) with
workflow steps adapted for each delivery surface.
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

devin-ai-integration[bot]

This comment was marked as resolved.

Addresses Devin Review feedback: all paste-into-Devin prompts now use
triple-backtick fenced code blocks per AGENTS.md rules. Also removes
redundant Desktop integration callout (content already in Tip block).

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 new potential issues.

View 5 additional findings in Devin Review.

Open in Devin Review

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 DeepWiki references omitted from Desktop and CLI variants

The Cloud variant (README.md) includes "Step 3 (Optional): Read the DeepWiki" in each lab, but both new variants (README.local.md and README.platform.md) omit this step entirely. The REVIEW.md rule says "Knowledge notes, DeepWiki, MCP integrations, and playbooks should be referenced where relevant." The omission is likely deliberate: the local/desktop variants replace the DeepWiki step with a hands-on monitoring/iteration step that better fits the local workflow. However, a brief mention (e.g., "See also the repo's DeepWiki for architecture context") would satisfy the shared-context-layer rule without disrupting the flow.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acknowledged — this is intentional. The local/desktop variants replace the "Read the DeepWiki" step with hands-on exploration steps (running devin locally, using Cascade for code exploration) which serve the same purpose of understanding repo architecture but through direct interaction. The Cloud variant keeps DeepWiki as a separate step because it's browser-based. Will leave as-is since the local workflow achieves the same goal through a different path.

Comment thread workshops/quality-engineering/README.local.md Outdated
…locks

Converts 6 standalone operational prompts from italic format to fenced
code blocks: coverage analysis, subagent delegation, mutation iteration,
app setup, and performance analysis prompts.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 new potential issues.

View 7 additional findings in Devin Review.

Open in Devin Review

Comment thread workshops/quality-engineering/README.local.md Outdated
Comment on lines +91 to +95
```
Analyze the current test coverage. Run the existing tests and generate a
coverage report. What are the top 5 modules with the lowest test coverage?
What testing patterns does the codebase use?
```

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 CLI variant prompts intentionally omit repo names due to local context

The AGENTS.md rule states "Prompts must include repo names, file paths, and expected output format." In README.local.md, most prompts omit the repo name (e.g., line 91-95 says "Analyze the current test coverage" without naming the repo). This is because the CLI workflow has the user cd into the repo and run devin first (e.g., lines 84-87), so Devin already has project context. The cloud variant (README.md) and platform variant (README.platform.md) correctly include repo names since their prompts are sent to cloud agents without local context. This is a deliberate adaptation, not an oversight — but it's worth noting that the AGENTS.md rule doesn't explicitly carve out an exception for CLI-context prompts.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct — this is deliberate. In the CLI workflow, users cd into the repo and run devin, so the agent already has full project context. Including the repo name in the prompt would be redundant since Devin CLI inherits the working directory. The cloud/platform variants include repo names because those prompts go to agents without local filesystem context.

Rename 'Subagent A/B' to 'Session A/B' since these are independent CLI
sessions in separate terminals, not subagents within a single session.
Aligns with Repos Required section which already used 'Session B'.
- **Leverage shell integration.** Devin CLI understands your shell context, recent commands, and terminal state — no need to re-explain your environment.
- **Iterate fast locally.** The local workflow lets you review changes instantly (`git diff`), test them immediately (`npm test`), and refine your instructions in real time.
- **Build up knowledge as you go.** Save testing conventions (framework choices, assertion style, test data patterns) as Knowledge items — they apply to CLI sessions too.
- **Hand off to Cloud when needed.** Some labs (scheduled sessions, long-running tests) benefit from Cloud execution. Use `devin --cloud` or hand off mid-session when the task outgrows local resources.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The devin --cloud flag referenced on line 42 of workshops/quality-engineering/README.local.md does not exist in the Devin CLI. The correct mechanism for cloud handoff is the /handoff slash command inside an interactive CLI session.

Line 42 currently reads:

Use `devin --cloud` or hand off mid-session when the task outgrows local resources.

Should be updated to something like:

Use the `/handoff` command inside a CLI session to send the task to Cloud when it outgrows local resources.

This was identified as the same mistake found and fixed in PR #128 (security demos).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant