Skip to main content
skill CX Codex

report-issue · microsoft, mobile-apps — Claude Code skill: bug report setup

report-issue collects project details and diagnostics, then drafts a GitHub issue for the mobile-app plugin. Use it to document a bug, unexpected result, or documentation problem.

MIT ★ 1,167 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add microsoft/power-platform-skills
/plugin install mobile-app@power-platform-skills
Open on GitHub

What report-issue does

The skill asks for a description, category, and severity before checking the mobile project environment. It can gather Node, npm, and CLI versions, inspect project context, and check native package versions when they are relevant to the report. For diagnostics, it may run npx --no-install expo doctor and collect suitable logs or TypeScript output.

It produces a structured issue draft with environment details, reproduction steps, and expected versus actual behavior. A link to the new issue form is included; the skill does not submit the report. Project checks are read-only.

The workflow excludes .env, node_modules, and sensitive tenant or organization identifiers from the report. Still review pasted errors and logs before filing. Node and npm are used for the checks, and some diagnostics depend on the tools available in the project environment.

What it helps with

  • turn a bug description into a GitHub issue draft
  • collect CLI versions and mobile project context
  • attach relevant build logs or TypeScript output
  • write down reproduction steps and expected behavior

Example prompts for the agent

  • Prepare a GitHub issue for a mobile-app build failure; the app was expected to launch but the build stopped.
  • Gather diagnostics for an issue involving a native package and draft the report.
  • Write an issue draft about incorrect mobile-app documentation.

How to install report-issue

1Plugin marketplace

/plugin marketplace add microsoft/power-platform-skills
/plugin install mobile-app@power-platform-skills

This installs the whole mobile-app plugin with all its skills

2Skills CLI (Vercel)

npx skills add microsoft/power-platform-skills --skill report-issue -a claude-code

3Manually: put the files in place

~/.claude/skills/report-issue/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/report-issue/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about report-issue

How do I install report-issue in Claude Code?

Add the marketplace with /plugin marketplace add microsoft/power-platform-skills, then install the plugin with /plugin install mobile-app@power-platform-skills.

What does report-issue do?

It gathers a problem description and relevant project diagnostics, then drafts a GitHub issue for the mobile-app plugin. You review and submit the issue yourself.

What information does the skill keep out of a public report?

It excludes .env contents, node_modules, and sensitive tenant or organization identifiers. Review error text and logs before submitting, too.

Source text

SKILL.md · MIT
---
name: report-issue
description: Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
user-invocable: true
argument-hint: "[optional: brief description of the bug]"
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
model: haiku
---

> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.

**📋 Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read this first.

# Report Issue — mobile-app

Generates a fully-populated GitHub issue body for the `microsoft/power-platform-skills` repo, scoped to the `mobile-app` plugin. Read-only — no project modifications.

## Workflow

1. Capture user description → 2. Detect project context → 3. Collect diagnostics → 4. Render issue body → 5. Print URL

---

### Step 1 — Capture user description

**Telemetry checkpoint: `capture_issue_description`**

If `$ARGUMENTS` contains a description, use it. Otherwise prompt:

> "What's the issue? Briefly describe what you expected vs. what happened. (You can paste error output if helpful.)"

Then ask via `AskUserQuestion`:

> "Issue category?
> (a) Bug — something broke
> (b) Unexpected behavior — wrong output but no error
> (c) Documentation — docs are wrong / missing
> (d) Feature request
> (e) Question / discussion"

> "How blocking is this?
> (a) Blocking — can't proceed at all
> (b) Workaround exists — but painful
> (c) Annoying — non-critical
> (d) Polish — nice-to-have"

### Step 2 — Detect project context

Read-only checks:

```bash
test -f power.config.json && echo "in_project=true" || echo "in_project=false"
pwd
node --version
npm --version
node scripts/resolve-environment.js "$(node -e \"console.log(require('./power.config.json').environmentId)\")" 2>/dev/null || true
az --version 2>/dev/null | head -1
npx --no-install expo --version 2>/dev/null
uname -srm
```

If in a project:

```bash
node -e "console.log(require('./package.json').name, require('./package.json').version)" 2>/dev/null
node -e "console.log(JSON.stringify({env: require('./power.config.json').environmentId, name: require('./power.config.json').displayName}))"
test -f memory-bank.md && echo "memory_bank=present"
test -f native-app-plan.md && echo "plan=present"
ls src/generated/services/ 2>/dev/null | head -10
```

If the description names a package matching `@microsoft/power-apps-native-*`, collect its declared and lockfile-resolved versions from `package.json` and `package-lock.json`. Do not read package source or metadata from `node_modules/`.

```bash
node - <<'NODE'
const fs = require('node:fs');
const manifest = JSON.parse(fs.readFileSync('package.json', 'utf8'));
const lockfile = fs.existsSync('package-lock.json')
  ? JSON.parse(fs.readFileSync('package-lock.json', 'utf8'))
  : null;
const dependencies = { ...manifest.dependencies, ...manifest.devDependencies };
for (const [name, declared] of Object.entries(dependencies)) {
  if (!name.startsWith('@microsoft/power-apps-native-')) continue;
  const resolved = lockfile?.packages?.[`node_modules/${name}`]?.version ?? 'unknown';
  console.log(`${name}\tdeclared=${declared}\tresolved=${resolved}`);
}
NODE
```

For native-build issues also capture:

```bash
[ "$(uname)" = "Darwin" ] && xcode-select -p
[ "$(uname)" = "Darwin" ] && pod --version 2>/dev/null
java -version 2>&1 | head -1
echo "ANDROID_HOME=$ANDROID_HOME"
```

### Step 3 — Collect diagnostics

**Telemetry checkpoint: `collect_issue_diagnostics`**

Run `npx --no-install expo doctor` and capture the text output verbatim.

Ask for the affected workflow's Support ID when available. Use the telemetry
helper's read-only `--report` mode from the affected project to inspect only its
allowlisted timeline. Include the Support ID and relevant step/error category in
the issue body, not environment, tenant, or organization IDs. Do not
upload the telemetry directory or raw timing/authentication files.

If the user pasted an error, capture verbatim. Otherwise look for recent failure signals:

- Last 50 lines of any Metro / Gradle / Xcode log if user mentions a build failure
- `git status --short` if in a git repo (to show modified files — sanitize for secrets first)
- Output of `npx --no-install tsc --noEmit` if relevant

**Do NOT capture:**
- Contents of `src/playerConfig.ts` (contains tenantId / clientId — sensitive)
- Contents of `.env` or any file matching `.env*`
- Connection IDs unless the user explicitly opted in (PII / can map to tenant)
- Anything under `node_modules/`
- Package source excerpts, patched package contents, or proposed fork code
- Tenant/environment/organization IDs in a public issue, even though verified
  IDs can exist in access-controlled telemetry

### Step 4 — Render issue body

**Telemetry checkpoint: `render_issue_report`**

Print this block — user copies into a new issue:

```markdown
### Description

<user's description>

### Category

<Bug / Unexpected behavior / Docs / Feature / Question>

### Severity

<Blocking / Workaround / Annoying / Polish>

### Environment

| | |
|---|---|
| Plugin | mobile-app |
| Plugin version | <from .plugin/plugin.json, or legacy .claude-plugin/plugin.json fallback, or "unknown"> |
| OS | <uname output> |
| Node | <version> |
| npm | <version> |
| Power Apps CLI | <version> |
| Expo CLI | <version> |
| Xcode | <if macOS> |
| JDK | <if android> |
| ANDROID_HOME set | <yes/no> |

### Project context

<if in project>
- Mobile project detected: yes
- Support ID: `<affected workflow run GUID, or unavailable>`
- Failed step / error category: `<registered step and fixed category, or unknown>`
- Memory bank present: <yes/no>
- Plan present: <yes/no>
- Connector count: <count, not generated service or business-table names>
</if>

<if not in project>
Not run inside a mobile-app project.
</if>

### Affected native package

<include only when the issue concerns @microsoft/power-apps-native-*>
- Package: `<package name>`
- Declared version: `<package.json range>`
- Resolved version: `<package-lock.json version or unknown>`
- Platform: `<iOS / Android>`
- Ownership evidence: <why the documented caller contract is satisfied and the failure is package-internal>

### Reproduction steps

1.
2.
3.

### Expected

<what should have happened>

### Actual

<what happened>

### Logs / errors

```
<paste verbatim — sensitive values redacted>
```

### Notes

<anything else>
```

### Step 5 — Print URL

**Telemetry checkpoint: `generate_issue_submission_url`**

Tell the user:

> Open this URL to file the issue:
>
> <https://github.com/microsoft/power-platform-skills/issues/new?labels=plugin%3Amobile-app>
>
> Paste the block above into the body. Review for any sensitive values before submitting.

If the user wants to open it, suggest `open <url>` (macOS) / `xdg-open <url>` (Linux) / `start <url>` (Windows). Do not auto-open without confirmation.

## Notes

- This skill never modifies any file or invokes mutating commands. Pure diagnostic.
- For diagnosing connection-specific failures, suggest the user run `/list-connections` first and paste that output into the issue.
- For diagnosing build failures, suggest they include the full Metro/Gradle/Xcode log (not truncated).

© Microsoft · MIT · microsoft/power-platform-skills

Similar skills

All skills for Mobile →

report-issue by other authors comes first.

report-issue Microsoft The report-issue skill guides a GitHub issue for a bug or other problem with the model-apps plugin. Use it when you want to report an issue. CX Codex +1 ★ 1,167repo stars report-issue Microsoft report-issue drafts Process Intelligence bug reports and support summaries for failed operations without exposing sensitive data. CX Codex +1 ★ 1,167repo stars scenario-report scenario-labs scenario-report is a Claude Code skill that prepares reproducible Scenario bug reports or change requests, gathers diagnostics, and checks sensitive details before publication. CX Codex +1 914installs issue-tracer2 ZaxbyHub issue-tracer2 pulls in a GitHub Issue, works through a chain of hypotheses to pin down the root cause, and carries the fix through to tests and a PR. CX Codex +1 ★ 539repo stars fix-issue frappe fix-issue turns a bug report into a fix: a subagent extracts the facts, the main agent reproduces the bug and traces the cause without inheriting the reporter's guesses. CX Codex +1 431installs codex-issue-coordinator owainlewis codex-issue-coordinator is a Codex skill that assigns GitHub issues to AI workers, tracks PRs and tests, and merges completed work. It handles batches in one Codex conversation. CX Codex +1 241installs issue-reporting manojbajaj95 issue-reporting turns a complaint about a GTM skill into a GitHub issue maintainers can act on: it collects the details, sorts the failure type and prefills the bug template. CX Codex +1 118installs post-issue-comment dyoshikawa The post-issue-comment skill reads a GitHub issue, drafts a concise English reply, and posts it. Use it when the response needs to reflect the existing discussion. CX Codex +1 ★ 1,636repo stars

From the same set157

The whole set →
manage-flows manage-flows manages Power Automate flow lifecycles in Claude Code: handles publish-test loops, batch changes, tenant inventories, and runaway run cancellations. CX Codex +1 ★ 1,167repo stars add-datasource The add-datasource skill identifies the data an Expo/React Native app needs and directs the request to the matching Power Platform skill. CX Codex +1 ★ 1,167repo stars canvas-create-discovery canvas-create-discovery — a subagent that scans Power Apps to map available controls, data sources, and APIs, then documents feasible design choices and constraints. Use it to validate your canvas app concept before implementation begins. CX Codex ★ 1,167repo stars check-updates check-updates is a Claude Code skill that sequentially checks and updates direct dependencies in Power Apps mobile projects, with type-checking, Expo validation, and rollback. CX Codex +1 ★ 1,167repo stars setup setup guides the agent through Process Intelligence configuration: dependency checks, cloud and environment selection, az login binding, then profile activation. CX Codex +1 ★ 1,167repo stars debug-flow debug-flow diagnoses failed Power Automate runs. It traces execution graphs, flags root causes, and prepares targeted flow fixes. CX Codex +1 ★ 1,167repo stars configure-canvas-mcp The configure-canvas-mcp skill connects Canvas Authoring MCP to an active Power Apps coauthoring session. Run it before editing a canvas app when the server is not connected yet. CX Codex +1 ★ 1,167repo stars add-sharepoint add-sharepoint connects SharePoint Online to Power Apps code apps: reads lists, manages documents, creates new lists via Graph API. CX Codex +1 ★ 1,167repo stars

Project sponsors

Companies that keep this analytics open