Chimney

Prepare and publish a pull request with a linked issue, English commit and PR titles, and a Chinese description explaining the change, implementation, and verification. Update an existing branch PR and report its URL and CI status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publishing current code changes as a pull request
• Rewriting a PR description to match the final changes
• Adding diagrams and rendered terminal output to a PR

Draft release notes that explain what changes for users. Verify the release range, reconcile commits and reversals, and highlight breaking changes, migration steps, and relevant pull requests with evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting release notes for a specific version
• Explaining breaking changes and migration steps
• Summarizing user-visible changes across pull requests

Review resolved dependency versions and relevant code for security vulnerabilities. Get findings with evidence, impact, and targeted remedies, distinguishing published dependency warnings from exploit paths demonstrated in the project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check dependencies for known vulnerabilities
• Trace untrusted input to sensitive operations
• Locate potential secrets in committed files

Answer questions about dsh-tui using its bundled manuals. Find relevant guidance on installation, shortcuts, configuration, themes, session migration, and VS Code integration, then cite the source file and section for checking.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up shortcuts and everyday operations
• Checking configuration and theme settings
• Finding guidance for migrating sessions

Turn existing pull request review comments into prioritized next steps by checking them against the current code. Separate outstanding concerns, addressed feedback, and questions needing replies, then implement and validate fixes when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prioritizing pull request review feedback
• Checking whether comments still apply to current code
• Implementing and validating requested review fixes

Review concrete code changes for defects, compatibility problems, repository-rule violations, and unnecessary code. Produce evidence-based findings and, when explicitly requested, make minimal cleanup changes while checking that existing behavior is preserved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request or commit range
• Inspecting staged and unstaged changes
• Finding debug residue and duplicate code

Audit a repository or broad subsystem for security, correctness, and maintenance risks. Trace how inputs reach affected behavior, verify suspected defects, and report confirmed findings with severity, triggers, impact, and practical remedies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing risks across a repository
• Checking state loss and resource limits in a TUI
• Checking dependencies for known vulnerabilities

Turn a reported defect into a concise bug report or issue draft that someone else can reproduce or investigate. Organize symptoms, reproduction steps, expected and actual behavior, environment, and impact while separating evidence from unknowns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a defect description into a bug report
• Organizing reproduction steps and expected behavior
• Adding evidence from logs and relevant code

Practice one programming concept through a small exercise matched to your goals, experience, and available time. Get feedback based on observable results, with hints or explained solutions and a harder variation when you are ready.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Practicing a programming concept in 10–15 minutes
• Understanding display width for CJK characters and emoji
• Tracing event order and cleanup