القائمة
Update project documentation in docs/ to reflect recent code changes, new features, or architectural decisions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run a comprehensive code quality audit and automatically create GitHub issues for every finding. Produces one .md file per issue, creates the GitHub issues with labels, adds them to the project board, then writes an audit-summary.md. Trigger when user asks for a code audit, quality review, tech debt scan, security review, or anti-pattern analysis. Accepts an optional path argument to scope the audit (e.g. /audit src/modules/auth). Without args, audits the full src/ directory.
Guides and best practices for working with Neon Serverless Postgres. Covers setup, local development, connection methods, Neon features, and platform tooling.
Update project documentation in docs/ to reflect recent code changes, new features, or architectural decisions.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Scaffolds NestJS DTOs with class-validator and @nestjs/swagger decorators.
Scaffolds unit tests (.spec.ts) for NestJS Services and Controllers, including automatic mocking of dependencies like UnitOfWork and Repositories.
| name | update-docs |
| description | Update project documentation in docs/ to reflect recent code changes, new features, or architectural decisions. |
| allowed-tools | Read, Grep, Glob, Bash, Edit, Write, Agent |
Review the recent code changes on the current branch and update the project documentation accordingly.
The docs live in docs/ with this layout:
docs/architecture/ — System design, module architecture, component descriptionsdocs/decisions/ — Architectural decision records (numbered sequentially)docs/workflows/ — Step-by-step flows (auth, sync, submission, etc.)docs/ROADMAP.md — High-level project roadmapIdentify what changed: Run git diff master...HEAD --name-only to see all changed files on this branch. Read the relevant source files to understand the changes.
Determine which docs need updating:
docs/architecture/docs/decisions/decisions.mddocs/workflows/Read existing docs first: Always read the doc file before editing to understand its style, structure, and what's already covered. Match the existing tone and formatting.
Update systematically:
docs/architecture/core-components.md — Update if tech stack, modules, cron jobs, or infrastructure changeddocs/decisions/decisions.md — Add new decision records with clear rationale and trade-offs[Caching](../architecture/caching.md))Keep it concise: Documentation should help developers understand why and how, not restate the code. Use tables for structured data, code blocks for examples, and mermaid diagrams where they add clarity.
$ARGUMENTS is providedFocus the documentation update on the topic specified: $ARGUMENTS