Results for “viewer”

Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, the seat for paying customers not in the room, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, customer-side risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a customer advocate review", "do a voice-of-the-customer pressure-test", "what would our customers say about this" or "what does this plan really ask of paying customers". Do not use for the product evidence or roadmap case, use cpo-reviewer instead; for revenue or pricing strategy, use cro-reviewer; for the staff who operate the change, use frontline-skeptic-reviewer. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

reviewer等から割り当てられたコード・設計・指示の対象を、指定された観点から評価する担当者向けの手順。担当配分・追加reviewer起動・結果の全体統合は行わない。

The English summary is being prepared. Showing the original description.

PR確認・PRレビューの依頼で、PRまたはremote branchの差分を取得しshared reviewerへ渡す。PR番号・URL・branchを扱い、ローカルの未コミット差分・ファイル指定はreviewerを使う。

The English summary is being prepared. Showing the original description.

Run the full implement-review-fix loop using implementer and reviewer personas. Supports effort-based multi-reviewer scaling (1-5 reviewers) with automatic specialization selection. Includes memory-based feedback loop that learns from past review patterns. Loops until all reviewers find 0 issues of any severity.

The English summary is being prepared. Showing the original description.

Turn before-and-after text or a patch into a view of changes. Create an interactive viewer URL, a PNG image, or a PDF so others can inspect edits and receive the comparison as an attachment.

• Sharing text changes through an interactive viewer
• Attaching a comparison as a PNG or PDF
• Preparing high-quality files for reviewing edits

Draft simple black-and-white screen layouts as standalone SVG files, with numbered explanations of each area. For multiple screens, create a flow overview and an optional static viewer page for browsing and zooming during review.

• Sketch a screen layout before implementation
• Review mobile and desktop screen structure
• Map a flow across multiple screens

Plan, draft, and revise academic papers with support for literature reviews, bilingual abstracts, citation checks, and responses to reviewers. The skill also formats manuscripts for publication requirements and produces Markdown, LaTeX, DOCX, or PDF outputs.

• Planning a paper’s structure and evidence
• Drafting a manuscript and bilingual abstracts
• Turning reviewer comments into a revision plan

Coordinate a research project from topic exploration to a final manuscript. The skill connects research, writing, integrity checks, review, and revision workflows, tracks deliverables, and records progress with user confirmation at stage boundaries.

• Taking a research topic through to a final manuscript
• Resuming a workflow from an existing draft or reviewer comments
• Tracking checks, revisions, and the paper creation process

Screen study titles, abstracts, and full texts against confirmed eligibility rules. Two AI reviewers assess records separately, with a third resolving conflicts, while outputs document exclusion reasons, selection counts, and the methods used.

• Define eligibility rules from a review protocol
• Screen titles, abstracts, and full texts
• Resolve conflicting screening decisions

Draft, review, or revise point-by-point peer review responses, revision cover letters, and marked manuscripts. The skill links claimed changes to manuscript locations, flags missing author input, and checks consistency across response letters and revised submission files.

• Draft point-by-point responses to reviewer comments
• Review an existing response for omissions and wording
• Prepare a revision cover letter

Review and improve statistical reporting in manuscript methods, results, and figure captions. It checks sample definitions, repeated measurements, tests, and uncertainty, then provides revised wording and identifies missing information or issues reviewers may raise.

• Reviewing a manuscript’s statistical methods section
• Checking sample sizes and repeated measurements
• Aligning figure captions with reported statistics

Turn a theme into generative art, artwork created by computational rules, using p5.js. Receive a written artistic philosophy and an interactive HTML viewer with adjustable parameters, reproducible variations, and PNG download controls.

• Creating generative art from a theme
• Exploring particle and flow-based compositions
• Comparing reproducible variations using seeds

Review a GitNexus pull request for production readiness with seven coordinated reviewer agents. Combine their findings and have a final critic check the draft, producing a review without editing code or posting results.

• Reviewing a GitNexus pull request before production use
• Combining findings from multiple reviewer agents
• Checking a review draft before finalizing it

Organize parallel code reviews across security, performance, architecture, testing, and accessibility. It helps assign review areas, merge duplicate findings, apply consistent severity ratings, and produce one report with locations, impacts, suggested fixes, and prioritized actions.

• Assigning review areas for a code change
• Merging duplicate findings from multiple reviewers
• Aligning severity ratings across review reports

Organize human review in Arize by defining label choices, numeric ranges, or free-text feedback fields. Manage review queues and reviewers, submit annotations for individual records, and apply existing labels to project spans, or individual processing records, in bulk.

• Define shared labels and scoring ranges for reviewers
• Create review queues and assign reviewers
• Record feedback on individual queue items

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Review a defined code change through independent code and architecture reviewers. Receive severity-rated findings with file and line references, concrete fixes, and a final recommendation on whether the change is ready to merge.

• Checking a pull request before merging
• Assessing code quality and security within a defined scope
• Reviewing architectural boundaries and hidden dependencies

Open existing PDFs in an interactive viewer to review pages together, highlight text, add comments or stamps, fill forms, and place signature images. Check changes visually and download the annotated document from the viewer.

• Reviewing contract terms with highlights and comments
• Filling PDF forms while checking the page
• Placing signature or initials images

Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.

• Understand how agent memories are stored and retrieved
• Plan extensions to agentmemory
• Check memory capture in the web viewer

Turn pull request changes, commits, and test evidence into a self-contained HTML guide. Explain the problem, system context, before-and-after behavior, and key code changes so reviewers know where to focus.

• Explain a complex pull request before review
• Show before-and-after behavior with diagrams
• Collect test evidence and review focus points

Design interview processes for specific roles and experience levels, with round objectives, timing, suggested questions, and scoring criteria. Help interviewers align their judgments and review potential bias before using the process.

• Designing interview rounds for a specific role
• Preparing questions for each interview round
• Aligning scoring criteria across interviewers

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

• Reviewing a pull request before merging
• Getting a second opinion on AI-written code
• Checking authentication or data access code

Customize cmux shortcuts, commands, workspace layouts, and viewer settings while preserving existing configuration. It identifies the right settings file, distinguishes app preferences from terminal preferences, and validates that actions and controls appear where expected.

• Adding a custom action to the Command Palette
• Saving project-specific workspace layouts and commands
• Adjusting viewer settings and browser routing

Review Pascal pull requests or branches against documented architecture rules. Check package responsibilities, node extension patterns, state management, and rendering subscriptions to identify misplaced code, compatibility breaks, and changes that could cause excessive redraws.

• Reviewing a Pascal pull request for architecture violations
• Auditing package responsibilities in a branch
• Checking new node definitions and scene compatibility