메뉴
Use when the user says "standup", "what did I do yesterday", or "/standup". Summarizes recent git activity across repositories into a standup-ready bullet list covering yesterday, today's plan, and blockers.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when reviewing a backend HTTP / GraphQL handler for validation, authz, errors, performance, observability, and security, or "/backend-review". Produces a structured review with file:line citations.
Use when running a cloud security posture scan (CSPM) on AWS, Azure, or GCP using prowler, scout-suite, or checkov, or "/cloud-scan". Requires read-only credentials; produces CIS-benchmark-aligned findings with remediation.
Use when scanning a container image or Dockerfile for vulnerabilities, misconfigurations, and best-practice violations using trivy, dockle, or hadolint, or "/image-scan". Flags base-image CVEs, root user, missing healthchecks, and bloat.
Use when running an authorized non-intrusive DAST baseline scan (OWASP ZAP baseline, nuclei, nikto) against a web app or API endpoint you own, or "/dast". Requires explicit authorization; refuses unowned targets.
Use when handed a stack trace, error log, or "this is broken" with a paste of output, and asked to find the root cause across frontend, backend, or DB tiers, or "/debug-trace". Produces a hypothesis tree, the evidence supporting each branch, and the next diagnostic step.
Use when scanning a project's third-party dependencies for known CVEs across npm, pip, Go, Maven, Cargo, etc., or "/dep-scan". Runs trivy, npm audit, pip-audit, govulncheck, or osv-scanner and produces a prioritized fix list.
| name | daily-standup |
| description | Use when the user says "standup", "what did I do yesterday", or "/standup". Summarizes recent git activity across repositories into a standup-ready bullet list covering yesterday, today's plan, and blockers. |
--since (default: yesterday 00:00).git config user.email).Resolve author. git config user.email.
For each repo, run:
git log --since="yesterday 00:00" --until="today 00:00" \
--author="<email>" --pretty=format:'- %s (%h)' --no-merges
Collect open work in progress:
git branch --show-currentgit status --shortgh pr list --author @me --state open --json number,title,url,isDraftFormat output:
**Yesterday**
- <commit subject> (<repo>@<sha>)
**Today**
- Continue <branch or PR>
- <planned items>
**Blockers**
- <if any, else "none">
If the user has a team template, honor it.
git log is empty, say so.