Communitygithub.com

cdcoonce/Portfolio_Website

AI-powered code quality analysis for Python, Markdown, and Mermaid diagrams. Use this skill when: (1) reviewing code for quality issues, (2) checking Python files for PEP8 violations, unused code, missing type hints, docstring problems, complexity issues, or potential runtime errors, (3) validating Markdown documentation for broken links, heading structure, or formatting issues, (4) validating Mermaid diagram syntax, (5) the user asks for a "code review" or "quality check", (6) analyzing code snippets pasted in conversation, or (7) suggesting and applying fixes for code quality issues.

Portfolio_Website 是什么?

Portfolio_Website is a Claude Code agent skill that aI-powered code quality analysis for Python, Markdown, and Mermaid diagrams. Use this skill when: (1) reviewing code for quality issues, (2) checking Python files for PEP8 violations, unused code, missing type hints, docstring problems, complexity issues, or potential runtime errors, (3) validating Markdown documentation for broken links, heading structure, or formatting issues, (4) validating Mermaid diagram syntax, (5) the user asks for a "code review" or "quality check", (6) analyzing code snippets pasted in conversation, or (7) suggesting and applying fixes for code quality issues.

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cdcoonce/Portfolio_Website/tree/HEAD/.claude/skills/daa-code-review

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档


name: daa-code-review description: AI-powered code quality analysis for Python, Markdown, and Mermaid diagrams. Use this skill when: (1) reviewing code for quality issues, (2) checking Python files for PEP8 violations, unused code, missing type hints, docstring problems, complexity issues, or potential runtime errors, (3) validating Markdown documentation for broken links, heading structure, or formatting issues, (4) validating Mermaid diagram syntax, (5) the user asks for a "code review" or "quality check", (6) analyzing code snippets pasted in conversation, or (7) suggesting and applying fixes for code quality issues.

DAA Code Review Skill

Analyze Python code, Markdown documentation, and Mermaid diagrams for quality issues. Combines external linters (ruff) with Claude's analysis to provide comprehensive code review with suggested fixes. Should not just be about running ruff and other linters, instead checks code for conformance with good software engineering practice (SOLID, DRY, YAGNI, simplicity not complexity); security vulnerabilities; and descriptive variable naming e.g. Don't do this:

pkb = p_key.private_bytes(
            encoding=serialization.Encoding.DER,
            format=serialization.PrivateFormat.PKCS8,
            encryption_algorithm=serialization.NoEncryption(),
        )

Instead do this:

private_key_bytes = p_key.private_bytes(
            encoding=serialization.Encoding.DER,
            format=serialization.PrivateFormat.PKCS8,
            encryption_algorithm=serialization.NoEncryption(),
        )

Quick Start

Analyze Python Code

from python_analyzer import analyze_python, analyze_python_file
from report_generator import generate_console_report, generate_markdown_report
from models import ReviewReport

# Analyze a code snippet
result = analyze_python(code_string)

# Analyze a file
result = analyze_python_file(Path("src/module.py"))

# Generate report
report = ReviewReport(results=[result], title="Code Review")
generate_console_report(report)  # Console output
markdown = generate_markdown_report(report)  # Markdown string

Analyze Markdown

from markdown_analyzer import analyze_markdown, analyze_markdown_file

result = analyze_markdown(content)
# or
result = analyze_markdown_file(Path("README.md"))

Analyze Mermaid Diagrams

For Mermaid validation, use Claude's understanding combined with web search for latest syntax. See mermaid-checks.md.

Workflow

  1. Receive code - From file path or pasted snippet
  2. Detect file type - Python (.py), Markdown (.md), or Mermaid (.mmd, code blocks)
  3. Run analysis - External linters first, then Claude's analysis
  4. Generate report - Both console and markdown formats
  5. Save report - Write markdown report to docs/code_reviews/{YYYY-MM-DD}_{file_name}.md (create directory if needed)
  6. Review fixes - Present suggested fixes to user
  7. Apply fixes - With user approval (flexible approval modes)
  8. Check README - Before pushing, verify README.md reflects current changes (new features, modified APIs, updated dependencies, changed configuration)

Analysis Capabilities

Python (via ruff + Claude)

CategoryExamplesSeverity
PEP8Line length, indentation, whitespaceWARNING/INFO
Unused CodeUnused imports, variables, argumentsWARNING
Type HintsMissing annotations on functionsINFO
DocstringsMissing/malformed numpy-style docstringsINFO
ComplexityFunctions with high cyclomatic complexityINFO
Runtime ErrorsUndefined names, syntax errorsERROR
ImportsUnsorted imports, banned importsINFO

Markdown

CheckDescriptionSeverity
Heading StructureProper h1→h2→h3 sequenceWARNING
Broken LinksFile links that don't existERROR
Missing Alt TextImages without accessibility textWARNING
FormattingTrailing whitespace, blank linesINFO
Code BlocksMissing language identifierINFO
Encoding CorruptionUTF-8 chars appearing as ×, âœ", etc.ERROR

Mermaid

Search web for latest Mermaid.js documentation before validating. Check:

  • Diagram type declaration
  • Node/edge syntax
  • Structural correctness
  • Relationship definitions

Output Formats

Console (Interactive)

Colorized output with severity indicators:

  • ✗ ERROR (red) - Must fix
  • ⚠ WARNING (yellow) - Should fix
  • ℹ INFO (blue) - Consider fixing

Markdown Report

Saved to docs/code_reviews/{YYYY-MM-DD}_{file_name}.md. For multi-file reviews, use a descriptive name (e.g., 2026-03-02_full_repo_review.md).

Structured report with:

  • Summary statistics
  • Status badge (Passed/Failed)
  • Issues table per file
  • Expandable issue details
  • Category breakdown

Fix Application

Fixes can be approved:

  • All at once - Apply all auto-fixable issues
  • By category - Apply all PEP8 fixes, skip docstrings
  • By severity - Fix errors first, then warnings
  • By file - Fix specific files only
  • Individually - Review each fix

See fix-workflow.md for detailed workflow.

Reference Documentation

Example Usage Patterns

Full Repository Review

User: "Review the code quality in my project"

1. List Python and Markdown files
2. Analyze each file
3. Aggregate into ReviewReport
4. Present console summary
5. Save report to docs/code_reviews/{YYYY-MM-DD}_full_repo_review.md
6. Offer to apply fixes

Quick Code Check

User: [pastes code snippet]
      "Any issues with this?"

1. Analyze snippet directly
2. Report issues inline
3. Suggest specific fixes

Pre-Commit Review

User: "Check these files before I commit"

1. Analyze specified files
2. Focus on errors and warnings
3. Block if errors found
4. Apply quick fixes if approved
5. Check if README needs updating based on changes
6. Update README if new features, APIs, or dependencies changed

Scripts

ScriptPurpose
models.pyData structures (Issue, Severity, AnalysisResult)
python_analyzer.pyPython analysis with ruff
markdown_analyzer.pyMarkdown quality checks
report_generator.pyConsole and Markdown report generation

Requirements

  • Python 3.10+
  • ruff (installed via pip)
  • Web access for Mermaid documentation lookup

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

cdcoonce/Portfolio_Website

Git commit workflow with enforced conventional commit style. Use when Claude needs to stage and commit changes, craft commit messages, or the user asks to commit, make a commit, or save their work. Ensures consistent commit message format, proper scoping, and atomic commits across the project.

cdcoonce/Portfolio_Website

Deploy the portfolio chat agent Lambda function to AWS. Use when the user asks to deploy, redeploy, push to Lambda, update the chat agent, or after updating context files or lambda_function.py. Rebuilds the knowledge base, packages dependencies, and deploys to AWS Lambda.

cdcoonce/Portfolio_Website

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

cdcoonce/Portfolio_Website

Orchestrate the full GitHub-issues-driven development lifecycle. 7-phase pipeline from brainstorm through PR with state tracking and cross-conversation resume. Use when user says "dev cycle", "development workflow", "full development pipeline", or invokes /dev-cycle.

cdcoonce/Portfolio_Website

Production Python coding standards with automatic version detection (3.10-3.13). Use when writing, reviewing, or refactoring Python to ensure adherence to modern type syntax, LBYL exception handling, pathlib operations, ABC-based interfaces, and production-tested patterns. Not Dagster-specific - applies to any Python project.

cdcoonce/Portfolio_Website

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

cdcoonce/Portfolio_Website

GitHub CLI (gh) integration for managing issues, pull requests, branches,

cdcoonce/Portfolio_Website

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

cdcoonce/Portfolio_Website

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

cdcoonce/Portfolio_Website

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when the user asks for a plan review, CEO review, mega review, or wants a plan challenged/stress-tested before implementation.

cdcoonce/Portfolio_Website

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

cdcoonce/Portfolio_Website

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in docs/plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

cdcoonce/Portfolio_Website

Generate or update the `.claude/docs/project.md` file that gives Claude project-specific context. Use this skill when the user asks to create, update, regenerate, or refresh project context, or says things like "update project.md", "generate project context", "this repo needs a project.md", or "Claude doesn't know about this project". Also trigger when onboarding Claude to a new repository for the first time.

cdcoonce/Portfolio_Website

Generate comprehensive, high-quality README.md files for code repositories. Use this skill whenever the user asks to create, write, generate, update, or improve a README for any project or repository. Also trigger when the user says things like "document this project", "write docs for this repo", "this repo needs a README", "help me onboard developers to this codebase", or asks for project documentation in markdown. Even if the user just says "README" or "readme" in the context of a codebase, use this skill.

cdcoonce/Portfolio_Website

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

cdcoonce/Portfolio_Website

Set up pre-commit hooks for the current repo. Use when user wants to add pre-commit hooks, configure commit-time linting, formatting, type checking, or testing. Triggers on "pre-commit", "git hooks", "linting hooks", or /setup-pre-commit.

cdcoonce/Portfolio_Website

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

cdcoonce/Portfolio_Website

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

cdcoonce/Portfolio_Website

Rewrites the prose sections of wiki pages in-place. Reads source files to understand current context, then updates only the content inside <!-- claude:prose --> ... <!-- claude:prose:end --> markers. Never touches <!-- generated:start --> ... <!-- generated:end --> blocks. Supports targeting a single page with /update-wiki {PageName}.

cdcoonce/Portfolio_Website

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

相关技能