Check the current project health status. Do the following:

1. Read `.issues/` directory and list all open issues (files with `open` in the name or status). Summarise each open issue in one line: ID, title, severity.

PublishedJun 7, 2026

Loading actions...

5 minBeginnerprompt4 files

Skill content

Main instructions and any bundled files for this skill.

markdown

Additional Files (3)

Check the current project health status. Do the following:

Read .issues/ directory and list all open issues (files with open in the name or status). Summarise each open issue in one line: ID, title, severity.
Run make lint and report pass/fail and any error count.
Run pytest -m "not expensive" --tb=no -q and report pass/fail and test count.
Check if docs/work_log.md has an entry from today — if not, flag it.
Report the MeetingBank data status: is data loaded in Supabase? (Check Issue #26 status.)

Present results as a concise status table. Flag any blockers that would prevent a demo.

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

Untitled Skill

193

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...

155

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

125

Jan 15, 2026