wjs-auditing-project
Use when the user asks to audit what's wrong with a project, "make it right", "看看项目出了什么问题", "为什么用户的需求还没上线", "为什么没提交App Store", "为什么没新build", or wants a holistic state-of-the-project check covering unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift (TODOS.md / ROADMAP), unreleased commits, and log errors. Runs read-only investigation, presents a grouped checklist, fixes only after explicit user confirmation. Aware of the Cathier iOS app workflow (Xcode + fastlane + auto-merge @claude PRs from in-app feedback).
npx skills add jianshuo/claude-skills --skill wjs-auditing-project --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# wjs-auditing-project ## Overview Holistic project-state audit. Find everything that's stalled, broken, or diverged from the plan — then fix it together after the user confirms the checklist. **Hard two-phase split:** 1. **Investigate → present grouped checklist** (read-only; no commits, no merges, no pushes) 2. **Fix** — only after the user explicitly confirms what to do Never collapse the phases. The user wants to see the full picture before any action. "Just go ahead and fix everything" is fine as confirmation, but you still produce the checklist first so they can scan it. ## When to use - "看看现在的项目到底出了什么问题" / "make it right" / "what's broken" - "为什么我的反馈还没上线" - "为什么很久没有新 build / 没提交 App Store" - "有没有 PR / 分支没合" - Returning to a project after time away - Before a release / TestFlight push, to make sure nothing is dangling ## Phase 1 — Investigate (parallel) Run all the read-only checks in **one message with parallel Bash calls**. Don't ask the user which to run; run them all. Many will return "nothing wrong" — that's fine, those just don't show up in the checklist. ### A. Working tree & stashes - `git status` — uncommitted work? - `git stash list` — forgotten stashes? - `git bran
- Overview
- When to use
- Phase 1 — Investigate (parallel)
- A. Working tree & stashes
- B. Open / draft PRs
- C. CI / GitHub Actions
- D. Released vs unreleased work (iOS specifics for Cathier)
- E. Plan drift
- F. App / system logs
- G. User-feedback specifically
- Presenting the checklist
- Phase 2 — Fix (only after user confirms)
- What you can do autonomously
- What requires the user to act
What does the wjs-auditing-project skill do?
Use when the user asks to audit what's wrong with a project, "make it right", "看看项目出了什么问题", "为什么用户的需求还没上线", "为什么没提交App Store", "为什么没新build", or wants a holistic state-of-the-project check covering unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift (TODOS.md / ROADMAP), unreleased commits, and log errors. Runs read-only investigation, presents a grouped checklist, fixes only after explicit user confirmation. Aware of the Cathier iOS app workflow (Xcode + fastlane + auto-merge @claude PRs from in-app feedback).
How do I install it?
Run `npx skills add jianshuo/claude-skills --skill wjs-auditing-project --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jianshuo/claude-skills, a repository with 112 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.