wjs-auditing-project

Solid

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).

AI & Automation 129 stars 21 forks Updated 3 weeks ago MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
70
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 branch -vv` — local branches, ahead/behind tracking - `git log --oneline main..HEAD` — what's on current branch not in main - `git fetch origin --prune && git log --oneline HEAD..@{upstream}` — what's on remote not local - `git branch -r --merged main` and `git branch -r --no-merged main` — re...

Details

Author
jianshuo
Repository
jianshuo/claude-skills
Created
4 months ago
Last Updated
3 weeks ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

project-audit

Deep audit of the whole repo — verify docs ↔ code alignment, score each feature group out of 100 against a best-available bar, and emit an exhaustive prioritized backlog that would bring every group to 100. Use when the user asks for a project audit, quality scores, "how good is this really", or "what's missing to make this perfect".

1 Updated 2 days ago
jrittelmeyer
Code & Development Listed

project-audit

Use when someone asks what is actually true of a whole project right now — what is finished, what is half-built, what is broken, and what nobody has looked at. Walks a cold start: discover what the project is, run a registry of probes chosen from that, read production evidence (published artefact against source, CI history, telemetry present or absent), then leave a self-contained HTML report and a JSON sidecar so the next audit can say what moved. Read-only: it proposes board rows and commits nothing. Triggers - 'project audit', 'audit the project', 'codebase audit', 'state of the project', 'what is unfinished', 'project health check', 'аудит проекта', 'проаудируй проект', 'состояние проекта', 'что не доделано', 'аудит кодовой базы'. Not for: auditing one deliverable inside a run (that is the pipeline's own ladder), reviewing a diff, or checking a skill's construction — say 'без диагностики' to opt out.

4 Updated today
ssheleg
Testing & QA Listed

project-audit

Run a full-spectrum senior engineering audit of an existing codebase or product across 15 domains — security, data, testing, architecture, API, DevOps, observability, performance, accessibility, SEO/web presence, privacy, docs, dependencies, DX and cost — producing a prioritised, verifiable findings report with a 0–100 scorecard. Use when the user says "audit my project", "review my codebase", "is this production ready", "what's wrong with my app", "health check", "due diligence", "technical assessment", "security review", "code review of the whole repo", "inherited this codebase", "what would a senior engineer say", "is this safe to launch", "find the problems" or shares a repository or URL and asks for an assessment. By Devleck.

3 Updated 2 weeks ago
Kin9Zeus