MCA Express Project Automation

Automated workflow for handling changes to the MCA Express Next.js application. This skill guides you through the complete process of reading GitHub issues, making requested changes, verifying code quality, and creating pull requests.

Project Context

**Technical Stack:**

**Key Content Locations:**

Workflow Steps

1. Understand the Request

Read the linked GitHub issue to identify what changes are being requested:

```bash

gh issue view <issue-number>

```

Parse the issue description to understand:

2. Execute the Changes

Make only the necessary modifications to the identified files. Common change types:

**Important:** Make surgical, focused changes. Do not refactor or "improve" unrelated code.

3. Verify Code Quality

Run verification checks in sequence. Both must pass before creating a PR.

**Lint Check:**

```bash

pnpm run lint

```

**Build Check:**

```bash

pnpm run build

```

**If either check fails:**

1. Do NOT create a pull request

2. Review the error messages

3. Either fix the issues or document why they cannot be resolved

4. Comment on the original issue explaining the failure

4. Skip Screenshots

**Important:** Do NOT attempt to take screenshots or run Playwright tests. The visual testing setup requires complex infrastructure and will cause failures in automated environments.

5. Create Pull Request

Only proceed if both lint and build checks pass.

**PR Title Format:**

```

[Type]: Brief description from issue

```

Examples:

**PR Body Template:**

```markdown

Closes #<issue-number>

Changes

Verification

```

**Create PR Command:**

```bash

gh pr create --title "[Type]: Brief description" --body "$(cat <<'EOF'

Closes #<issue-number>

Changes

Verification

EOF

)"

```

Safety Rules

1. **Never create a PR if checks fail** - Failing builds will cause deployment issues

2. **Read before writing** - Always read files before modifying them to understand context

3. **Minimal changes only** - Don't refactor, don't add features, don't "improve" code unless explicitly requested

4. **No screenshot attempts** - Skip all visual testing in automated environments

5. **Dependencies pre-installed** - The workflow has already run `pnpm install`, so skip this step

Performance Optimizations

Error Handling

When verification fails:

1. Read the error output carefully

2. Identify if it's a fixable issue (typo, syntax error) or project configuration issue

3. If fixable: make corrections and re-verify

4. If not fixable: comment on the issue with error details and stop the workflow

**Issue Comment Template for Failures:**

```markdown

Unable to create PR due to verification failure:

**Failed Check:** [lint/build]

**Error Output:**

```

<paste error here>

```

Please review the error and update the issue requirements if needed.

```

Constraints