Skip to content

Landing: current comparison; README links to pages instead of embedding map - #119

Merged
yourconscience merged 1 commit into
mainfrom
landing-refresh
Jul 17, 2026
Merged

Landing: current comparison; README links to pages instead of embedding map#119
yourconscience merged 1 commit into
mainfrom
landing-refresh

Conversation

@yourconscience

@yourconscience yourconscience commented Jul 17, 2026

Copy link
Copy Markdown
Owner
  • Landing "How it compares" table replaced: gstack/SuperClaude/skillshare (stale, not comparable) → rulesync/ruler/openskills with counts verified 2026-07-15 (docs/plans/launch-2026-07-14/05-landscape-facts.md); added Scope and Pinned+audited-externals rows; verification note under the table.
  • Landing "Get started" updated for v0.3.x: setup offers git init itself; skill creation via dotagents skill new.
  • Landscape section intro rewritten to the user-level vs project-level framing.
  • README: harness-map image removed; prominent "Overview & comparison →" link to the pages site instead.

Summary by Sourcery

Update the landing page and README to reflect current comparisons and getting-started flow, emphasizing dotagents’ user-level scope and directing users to the hosted overview site.

New Features:

  • Clarify the setup flow on the landing page, including git init offered by dotagents and skill creation via the CLI.
  • Add a refreshed comparison table on the landing page highlighting scope, harness coverage, and external skill pinning across related projects.

Enhancements:

  • Reframe the Landscape section copy around user-level versus project-level tooling and deepen the description of harness coverage and audited externals.
  • Simplify the README by removing the harness map image and replacing it with a prominent link to the hosted overview and comparison page.

@sourcery-ai

sourcery-ai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Landing page content is updated to reflect v0.3.x workflow and a more accurate competitive landscape, while the README now links to the external overview/comparison page instead of embedding the harness map image.

File-Level Changes

Change Details Files
Update the landing page setup and skill creation flow to match the v0.3.x CLI behavior.
  • Extend the setup description to mention git init being offered and preview of removals by harness.
  • Remove the explicit git init command from the quickstart shell snippet.
  • Switch the skill creation example from manual directory creation to dotagents skill new.
docs/site/index.html
Refresh the Landscape section framing and comparison table to focus on user-level versus project-level tools with verified counts.
  • Rewrite the Landscape section intro to emphasize user-level, deep harness coverage, and audited external skills.
  • Replace the comparison table columns from gstack/SuperClaude/skillshare to rulesync/ruler/openskills.
  • Adjust table rows to new comparison dimensions such as Scope, Pinned + audited externals, Harness coverage, and revised install methods.
  • Add a verification note below the table explaining counts and positioning among tools.
docs/site/index.html
Change the README call-to-action to point readers at the hosted overview/comparison page instead of an inline harness map image.
  • Replace the releases/landing page link line with a primary link to the overview & comparison site plus releases.
  • Remove the embedded harness map image from the README.
README.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 left some high level feedback:

  • The comparison table relies heavily on color and short "y/n" labels; consider adding more descriptive text or icons so the differences are clearer and more accessible to screen readers and color-blind users.
  • Inline styles are used repeatedly in the landscape comparison table (e.g., for gold text and padding); extracting these into CSS classes would simplify future maintenance and keep the HTML markup cleaner.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The comparison table relies heavily on color and short "y/n" labels; consider adding more descriptive text or icons so the differences are clearer and more accessible to screen readers and color-blind users.
- Inline styles are used repeatedly in the landscape comparison table (e.g., for gold text and padding); extracting these into CSS classes would simplify future maintenance and keep the HTML markup cleaner.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@yourconscience
yourconscience merged commit 9620df5 into main Jul 17, 2026
4 checks passed
@yourconscience
yourconscience deleted the landing-refresh branch July 17, 2026 17:37

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c3554910cb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/site/index.html
<div class="path-label" style="background:rgba(245,200,106,.12); color:var(--gold);">Private config</div>
<h3>Set up your home</h3>
<p class="desc">Detect harnesses, import existing content by copy, and run the first native sync.</p>
<p class="desc">Detect harnesses, import existing content by copy, offer git init, and run the first native sync. Removals are previewed per harness before anything is touched.</p>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Narrow the setup preview guarantee

setup does not wait for this removal preview before touching native configuration: runSetup calls patchAgentConfig for detected harnesses and the memory hook migration/cleanup helpers before it enables ConfirmRemovals and enters runSync, where the destructive-action preview runs. For users with Hermes/Amp config or legacy memory hooks, following this page can therefore modify harness config before the promised preview; please limit the claim to removal/overwrite actions or move the preview earlier.

Useful? React with 👍 / 👎.

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