Skip to content

Add portfolio page output: opening line, success hero, one card per automation - #1

Merged
RachaelQuisel merged 9 commits into
mainfrom
portfolio-page-success-hero
Nov 3, 2026
Merged

RachaelQuisel merged 9 commits into
mainfrom
portfolio-page-success-hero

Conversation

@RachaelQuisel

@RachaelQuisel RachaelQuisel commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

Iterates on the existing skill with a portfolio-page mode. It adds an opening line and hero stats stated once: $180,000 gross per year, about 5 hours a week and about 900 five-star reviews. It also adds the airbnbai.rent quote (20+ hours down to 5), sourced social proof (Guest favorite, 4.97 rating, top 5%, 600+ Airbnb and about 300 VRBO reviews) and a Book a call button in the hero and footer. The five-star standard video leads the La Maison section, followed by 8 cards with embedded videos and a separate Friendly task tracker card. Researched portfolio and LinkedIn patterns are included with sources. Time saved appears only when a source states it. Copy follows the proper-grammar skill with no em dashes. Not merged.

Summary by Sourcery

Add portfolio-page generation guidance that turns sourced automation evidence into a structured, video-led showcase.

New Features:

  • Add a portfolio-page output mode with a structured opening, hero statistics, sourced proof and calls to action.
  • Define a one-card-per-automation layout with embedded video proof, source links and evidence-based time-saved claims.
  • Add dedicated portfolio guidance covering La Maison automations, the Friendly task tracker and researched presentation patterns.

Enhancements:

  • Apply consistent grammar and punctuation refinements across the plugin documentation and reference material.

Documentation:

  • Document portfolio-page output requirements, evidence rules, source mapping and privacy constraints.

@sourcery-ai

sourcery-ai Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Introduces portfolio-page rendering guidance that turns the existing evidence-based review into an ordered portfolio: approved opening line, one-time success hero, and individually sourced automation cards with links, video thumbnails, and only substantiated time-saved claims.

Flow diagram for portfolio page rendering

flowchart TD
    A[Portfolio page request] --> B[Approved opening line]
    B --> C[Hero stats stated once]
    C --> D[Create one card per automation]
    D --> E[Add workflow or video link]
    E --> F[Add real video thumbnail]
    F --> G{Time saved sourced?}
    G -->|Yes| H[Show sourced time saved]
    G -->|No| I[Leave time saved out]
    H --> J[Portfolio page]
    I --> J
Loading

File-Level Changes

Change Details Files
Adds a dedicated portfolio-page output mode with a fixed evidence-based structure.
  • Routes portfolio-page requests to new reference guidance while preserving review behavior.
  • Requires the owner-approved opening line before all other content.
  • Defines a bold hero with one-time $200,000/year and about 5 hours/week callouts.
  • Requires one proof card per automation with its purpose and a public or access-appropriate link.
  • Specifies video poster or ffmpeg-generated thumbnails and prohibits invented time-saved claims.
  • Documents La Maison public, video, and private repository sources plus privacy and sample-data rules.
plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md
plugins/github-portfolio-builder/skills/github-portfolio-builder/references/portfolio-page.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 3 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="plugins/github-portfolio-builder/skills/github-portfolio-builder/references/portfolio-page.md" line_range="10-11" />
<code_context>
+1. **Opening line.** Use the owner's approved line word for word. For Rachael Quisel:
+   "Automating my vacation rental led me to a career I love. Now I help other business owners automate their work and get their time back."
+2. **Hero stats.** A bold section with big stat callouts, stated once, here only:
+   - **$200,000** gross per year (La Maison Santa Barbara short-term vacation rental)
+   - **About 5 hours a week** of her time, thanks to the automations
+   Do not repeat these figures elsewhere on the page.
+3. **The automations, one card each.** Never a single grouped highlight. Frame each card as proof of the hero result. Each card has:
</code_context>
<issue_to_address>
**Unsupported hero claims**

When the inspected sources do not substantiate the revenue or the automation-attributed time savings, the page prints these figures as established results even when inspected sources do not support them, including attributing the weekly time savings to the automations; visitors see unsupported business and outcome claims presented as fact.

Require a source for each hero statistic and its attribution, and omit or clearly qualify any claim the evidence does not support.
</issue_to_address>

### Comment 2
<location path="plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md" line_range="73" />
<code_context>
+
+## Build a portfolio page
+
+When the user asks for a portfolio page instead of a review, follow [references/portfolio-page.md](references/portfolio-page.md): the owner's opening line first, a bold hero with the headline stats stated once, then one card per automation with what it handles, a link, a thumbnail from its video, and time saved only when a source states it.
</code_context>
<issue_to_address>
**Review sections clutter the page**

When the user requests a portfolio page instead of a review, the unconditional output rule still adds Scope, Assessment, Priorities, and Limits, so the assistant returns review sections alongside the requested page instead of a standalone page.

Make the review-section requirement inapplicable to portfolio-page requests.
</issue_to_address>

### Comment 3
<location path="plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md" line_range="73" />
<code_context>
+
+## Build a portfolio page
+
+When the user asks for a portfolio page instead of a review, follow [references/portfolio-page.md](references/portfolio-page.md): the owner's opening line first, a bold hero with the headline stats stated once, then one card per automation with what it handles, a link, a thumbnail from its video, and time saved only when a source states it.
</code_context>
<issue_to_address>
**Portfolio mode stays undiscoverable**

When users or host selection rely on the skill or plugin descriptions to find the capability, the review-only descriptions omit portfolio-page creation, so users do not learn about the mode and host selection can skip the skill.

Update the skill and plugin descriptions to advertise portfolio-page creation.
</issue_to_address>

Sourcery assessment

Approval pending. 3 findings to address first.

Blocking findings: plugins/github-portfolio-builder/skills/github-portfolio-builder/references/portfolio-page.md:11, plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md:73, plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md:73


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment on lines +10 to +11
- **$200,000** gross per year (La Maison Santa Barbara short-term vacation rental)
- **About 5 hours a week** of her time, thanks to the automations

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Unsupported hero claims

When the inspected sources do not substantiate the revenue or the automation-attributed time savings, the page prints these figures as established results even when inspected sources do not support them, including attributing the weekly time savings to the automations; visitors see unsupported business and outcome claims presented as fact.

Require a source for each hero statistic and its attribution, and omit or clearly qualify any claim the evidence does not support.

Prompt for AI agents
In `plugins/github-portfolio-builder/skills/github-portfolio-builder/references/portfolio-page.md` at lines 10-11:

**Unsupported hero claims**

When the inspected sources do not substantiate the revenue or the automation-attributed time savings, the page prints these figures as established results even when inspected sources do not support them, including attributing the weekly time savings to the automations; visitors see unsupported business and outcome claims presented as fact.

Require a source for each hero statistic and its attribution, and omit or clearly qualify any claim the evidence does not support.


## Build a portfolio page

When the user asks for a portfolio page instead of a review, follow [references/portfolio-page.md](references/portfolio-page.md): the owner's opening line first, a bold hero with the headline stats stated once, then one card per automation with what it handles, a link, a thumbnail from its video, and time saved only when a source states it.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Review sections clutter the page

When the user requests a portfolio page instead of a review, the unconditional output rule still adds Scope, Assessment, Priorities, and Limits, so the assistant returns review sections alongside the requested page instead of a standalone page.

Make the review-section requirement inapplicable to portfolio-page requests.

Prompt for AI agents
In `plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md` at line 73:

**Review sections clutter the page**

When the user requests a portfolio page instead of a review, the unconditional output rule still adds Scope, Assessment, Priorities, and Limits, so the assistant returns review sections alongside the requested page instead of a standalone page.

Make the review-section requirement inapplicable to portfolio-page requests.


## Build a portfolio page

When the user asks for a portfolio page instead of a review, follow [references/portfolio-page.md](references/portfolio-page.md): the owner's opening line first, a bold hero with the headline stats stated once, then one card per automation with what it handles, a link, a thumbnail from its video, and time saved only when a source states it.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Portfolio mode stays undiscoverable

When users or host selection rely on the skill or plugin descriptions to find the capability, the review-only descriptions omit portfolio-page creation, so users do not learn about the mode and host selection can skip the skill.

Update the skill and plugin descriptions to advertise portfolio-page creation.

Prompt for AI agents
In `plugins/github-portfolio-builder/skills/github-portfolio-builder/SKILL.md` at line 73:

**Portfolio mode stays undiscoverable**

When users or host selection rely on the skill or plugin descriptions to find the capability, the review-only descriptions omit portfolio-page creation, so users do not learn about the mode and host selection can skip the skill.

Update the skill and plugin descriptions to advertise portfolio-page creation.

sourcery-ai[bot]
sourcery-ai Bot previously approved these changes Nov 3, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sourcery assessment

Approved.

@sourcery-ai
sourcery-ai Bot dismissed their stale review November 3, 2026 04:01

Sourcery withdrew this approval because the latest commits introduced blocking findings.

@RachaelQuisel
RachaelQuisel merged commit f0330f1 into main Nov 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant