Skip to content

docs(research-topic): split saving a topic into stage-research - #310

Open
si618 wants to merge 2 commits into
docs/follow-opinions-skillfrom
docs/split-research-topic
Open

si618 wants to merge 2 commits into
docs/follow-opinions-skillfrom
docs/split-research-topic

Conversation

@si618

@si618 si618 commented Nov 20, 2026

Copy link
Copy Markdown
Collaborator

What changed

  • research-topic now only answers: It answers a .NET question in the conversation, from the opinions first and then the vetted roster, with a source for every claim. It writes no file, starts no worktree, and opens no pull request. It closes with what the opinions don't cover, and where to raise it.
  • A new skill, stage-research, saves a topic: It holds what research-topic did in a checkout: the worktree, the worker fan-out, the compiled code samples, the advisory check, the topic under research/, and the research: pull request. It follows research-topic's steps for the scan, and adds the ones that saving needs.
  • The lifecycle is now stage, then resolve: The README, both diagrams, resolve-research, and the files under agents/ name stage-research where they mean saving a topic.

Checked with just verify, which redraws both diagrams.

This branch is stacked on #309, so merge that first. Not checked: an agent run of either skill.

Why

research-topic does two jobs. Most of it describes saving a topic in this repository, and one paragraph tells a reader outside a checkout to skip about half of it. The usage pages send every reader to it from their own project, where only that paragraph applies.

The site is starting to publish the skills a project runs, in awesome-humans/website#222. A published skill installs into someone else's project, so it can't link agents/ files or assume a checkout. With the split, research-topic is that skill, and the site can publish it as research-dotnet-topic beside follow-dotnet-opinions and review-dotnet-project.

Still to follow, outside this repository: the website's pages and diagrams, and the organisation's pull request templates, name research-topic where they mean saving a topic.

Refs: awesome-humans/website#159
Refs: #309

@coderabbitai

coderabbitai Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Central YAML; Path: .coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: d2fb0810-7d06-408e-9d06-65537bcbbbc4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

This branch was successfully deployed

1 active deployment
preview — 1724ed12 Deployed Nov 21, 2026 by si618 via deploy / deploy #350
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