[Bug] android-cli: malformed JSON example in journeys.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- android
- Domain
- cli, documentation
Research direction
Open references/journeys.md and locate the "Summarizing" section. Replace the malformed example with fenced, parseable JSON using closed strings and no comments or trailing commas, then move the field explanations into a separate "Field reference" list. Done means the example can be parsed as JSON and documents the requested fields and status values.
Written by the indexing model from the issue text.
Description
Affected Skill
devtools/android-cli
Description
The "Summarizing" section of references/journeys.md shows example output that isn't valid JSON:
- Fenced as a plain code block (not
```json) - Contains inline
//comments (not valid JSON) - Has a malformed key (
"journey:",) - Has an unterminated string (
"action": "Click the blue button,) - Has trailing commas after the last property in each object
Expected Behavior
The example should be valid, parseable JSON, since the instruction given is "output JSON describing the results."
Actual Behavior
The example block cannot be parsed as JSON. This risks an agent copying the same malformed structure (comments, trailing commas, unterminated strings) into its actual output when following this section.
Steps to Reproduce
- Open
references/journeys.md→ "Summarizing" section. - Try to parse the example block as JSON → fails (unterminated string, trailing commas,
//comments, malformed"journey:",key).
Suggested Fix
Fence the example as ```json with valid syntax (closed strings, no trailing commas, no inline comments), and move the field explanations (meaning of status, commands, comment, valid status values) into a separate "Field reference" list below the example.
- Dominant language
- Python
- Stars
- 7.5k
- Forks
- 486
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from android/skills
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
[Feature] Add fused-location skill for foreground FLP, Android 12 permissions, and update lifecycle Open
Difficulty 2/5 Half a day Newbie friendliness 82/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100