desktop-app-fallback
Manual Post-Write QA chain for Claude Code Desktop App (hooks don't fire)
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- desktop-app-fallback
- owner
- test-runner
- scope
- co-abap
- status
- active
- version
- 1.0.0
- metadata
- { "type": "task", "triggers": [ "desktop-app-fallback", "manual QA", "Desktop App" ] }
- description
- Manual Post-Write QA chain for Claude Code Desktop App (hooks don't fire)
- last_reviewed
- 1786752000000
- prerequisites
- Claude Code Desktop App
03 SKILL.md 正文
Desktop App Post-Write Fallback
When to Use
Use this skill when working in the Claude Code Desktop App, where PostToolUse hooks do not fire automatically.
Trigger
After any WriteSource or EditSource operation in the Desktop App.
Manual QA Chain
Run the following commands manually after each write operation:
# 1. Syntax Check
vsp syntax check --object "<object_url>"
# 2. Run Unit Tests
vsp test run --object "<object_url>"
# 3. Run ATC Check
vsp atc run --object "<object_url>"
Or Use the Combined Script
bun scripts/post-write.ts "<object_url>"
Expected Results
| Step | Required | Action on Fail |
|---|---|---|
| Syntax Check | ✅ Pass | Fix syntax errors, re-run |
| Unit Tests | ⚠️ Best effort | Fix bugs if critical |
| ATC Check | ✅ P1 must pass | Fix P1 findings, document P2/P3 |
After QA Pass
- Sync changes:
bun scripts/sync-mcp.ts - Commit:
bun scripts/dev-sync.ts "description"
Context
The Claude Code Desktop App does not automatically fire PostToolUse hooks after write operations, meaning the standard post-write QA chain is bypassed. This skill provides a manual fallback so developers can still enforce syntax checking, unit testing, and ATC validation after every ABAP write operation in Desktop App sessions.
Execution Steps
- Syntax Check — Run
vsp syntax check --object "<object_url>"and verify pass. - Unit Tests — Run
vsp test run --object "<object_url>"and review results. - ATC Check — Run
vsp atc run --object "<object_url>"and ensure no Priority-1 findings. - Alternatively, run the combined script:
bun scripts/post-write.ts "<object_url>". - After QA passes, sync changes with
bun scripts/sync-mcp.tsand commit withbun scripts/dev-sync.ts.
Output Format
Pass/fail result for each QA step:
- Syntax Check: Pass required; fix and re-run on failure.
- Unit Tests: Best effort; fix critical bugs.
- ATC Check: Priority-1 must pass; document Priority-2/3 findings.
Related Skills
- post-write-chain — The automated version of this chain for CLI sessions where hooks fire
- abap-dev — Core ABAP development workflows that precede the write operations
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.