'systematic' 검색 결과

Explore a web application as a user to find bugs and usability problems. Produce a structured report with reproducible steps, screenshots, and videos for interaction issues, giving responsible teams clear evidence to investigate.

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

• Checking core workflows before release
• Finding usability problems in forms and navigation
• Preparing bug reports with reproduction evidence

Investigate bugs, failed tests, and unexpected behavior through reproducible steps, evidence gathering, and comparison with working code. Test one hypothesis at a time, then implement a focused fix and verify it with tests.

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

• Investigating failed tests or builds
• Tracing production bugs across components
• Reassessing a problem after repeated failed fixes

Audit TypeScript projects for type-only imports, duplicate imports, missing base class inheritance, and incomplete public exports through index.ts files. Apply targeted fixes in a defined order and check compilation with tsc --noEmit.

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

• Separate type-only imports from runtime imports
• Consolidate duplicate imports from the same module
• Check classes for missing base class inheritance

Build TypeScript interface panels with badges, thumbnails, and colors driven by data. Organize shared behavior in a base class, including fetch retries, error recovery, and saved panel size and expansion state.

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

• Building a news panel with thumbnails
• Adding badges colored by data source
• Preserving panel size and expansion state

Diagnose connection problems with government websites by checking SSL certificates, which verify website identity, and proxy settings. Follow structured troubleshooting steps, record failed attempts, and explore alternative APIs or data sources when access remains blocked.

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

• Diagnosing certificate errors on government websites
• Checking whether proxy settings block data access
• Finding alternative sources for inaccessible public data

Troubleshoot access to government and institutional websites by checking connectivity, SSL certificates, and proxy settings. Follow a structured process to test request options, configure retries, and identify alternative data sources when access fails.

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

• Investigating SSL certificate errors
• Comparing browser and script connectivity
• Checking proxy authentication failures

Delegate file creation to shell_agent when direct generation tools fail. Specify the required format and content, then locate generated files by extension or modification time, copy them to the working directory, and check their integrity.

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

• Recover from failures in direct file generation
• Delegate PowerPoint creation with specific requirements
• Generate a PDF report containing charts and tables

Build a Web3 application that interacts with a blockchain, from contract interfaces and frontend screens to tests and deployment scripts. Package source code, configuration templates, and setup documentation into a ZIP for delivery.

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

• Building contracts and frontend screens together
• Creating wallet connections and contract interaction forms
• Preparing deployment scripts and address configuration

Diagnose failed connections to government websites and corporate portals by checking network access, SSL certificates, and proxy settings. If access remains unavailable, the workflow helps identify alternative data sources and document attempts and next steps.

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

• Investigating SSL certificate errors
• Checking connections through a corporate proxy
• Finding alternative sources for inaccessible data

Diagnose unclear failures from run_shell commands through a stepwise workflow. Capture error output, verify directories and command availability, check environment variables, and test simpler commands to narrow down problems with paths, permissions, or the execution environment.

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

• Investigating unknown errors returned by run_shell
• Comparing local and agent execution environments
• Checking paths, permissions, and command availability

Debug PowerPoint generation with python-pptx, a Python library for presentations. Follow a sequence of installation checks, minimal tests, error logging, and fixes for tables and charts, then inspect the generated slides.

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

• Diagnosing errors in PowerPoint generation
• Fixing table and chart code
• Saving detailed error logs

Diagnose Python spreadsheet failures through staged checks of the interpreter, library imports, file access, and basic operations. Minimal test scripts help separate environment problems from errors in the full processing script.

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

• Investigating unclear errors returned by run_shell
• Diagnosing spreadsheet scripts that suddenly stop working
• Checking Python setup in a new environment or container

Locate missing files and verify their full paths before processing them. This workflow checks directory contents, searches by filename, and inspects permissions, size, and modification time to help resolve FileNotFoundError, an error indicating a file could not be found.

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

• Investigating FileNotFoundError
• Finding files with unknown locations
• Checking file existence and permissions before processing

Track every required output in tasks involving multiple files, reports, or recipients. Build a checklist, update each item with completion evidence, and review the original requirements before declaring the task finished.

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

• Track a report and presentation requested together
• Check that documents for every department are complete
• Verify all named files exist before finishing

Troubleshoot PDF creation by trying pandoc, then reportlab, then fpdf2. Check tool availability, install missing Python libraries as needed, run generation with an explicit working directory, and verify that the output file exists.

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

• Converting Markdown or HTML to PDF
• Trying another tool after PDF generation fails
• Checking PDF tools and installing missing libraries

Diagnose PDF conversion failures in pandoc by checking installed conversion engines, capturing full error logs, and investigating missing fonts or packages. Follow a structured sequence of retries and fallback methods to find a working conversion route.

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

• Investigate an unknown error during PDF conversion
• Check which PDF engines are installed
• Find missing fonts or LaTeX packages

Troubleshoot unclear errors when converting documents to PDF with pandoc. Check installation, capture error logs, identify missing fonts or packages, and try alternative PDF engines, the tools that render the final document.

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

• Investigating an unknown error during PDF conversion
• Checking missing fonts and LaTeX packages
• Retrying conversion with a different PDF engine

Diagnose failed pandoc PDF conversions by checking installed tools, capturing error logs, and trying alternative PDF engines. The workflow helps identify missing fonts or packages and suggests ways to simplify documents when conversion still fails.

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

• Investigating unknown errors during PDF conversion
• Finding missing fonts or LaTeX packages
• Choosing a PDF engine for a document

Generate Word, PDF, and HTML documents from Markdown while diagnosing conversion failures. The workflow checks required tools, replaces problematic characters for PDF, tries alternative conversion engines, and verifies the resulting files.

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

• Diagnosing PDF encoding errors
• Exporting a report to Word, PDF, and HTML
• Investigating unclear document conversion failures

Evaluate vulnerability reports using seven practical criteria, including attacker capabilities, real usage, documented behavior, and remediation costs. Produce a reasoned decision to accept, dismiss, or request more evidence before committing to deeper investigation.

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

• Screening AI-generated security findings before human review
• Assessing whether a reported CVE warrants investigation
• Reviewing bug bounty submissions

Verify a reported security bug by tracing inputs, checking attacker capabilities, and examining existing protections. Produces a documented TRUE POSITIVE or FALSE POSITIVE verdict for each finding, with deeper verification for complex cases.

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

• Checking whether a reported vulnerability is real
• Verifying the conditions needed to exploit a finding
• Reviewing suspected false positives

Assesses smart contract and blockchain codebases against Trail of Bits’ nine-category maturity framework. Produces evidence-backed ratings covering areas such as arithmetic, access controls, documentation, and testing, plus a prioritized improvement roadmap with effort estimates.

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

• Assessing the maturity of a smart contract project
• Identifying gaps in tests and documentation
• Reviewing access controls and operational practices together

Assess how applications use encryption, signed tokens, and random values. Identify implementation weaknesses, select relevant testing tools, and document causes and fixes for issues involving encryption modes, RSA parameters, predictable randomness, and key derivation.

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

• Assessing encrypted cookies and tokens
• Checking RSA keys and cryptographic settings
• Testing session token predictability

Manage Reddit account activity through a staged 30-day plan, progressing from browsing and voting to comments and brand promotion. Track daily work, publishing approvals, account progress, and follow-up replies using local records.

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

• Start a staged activity plan for a new Reddit account
• Manage daily Reddit tasks and progress
• Review comment and post drafts before publishing