undefined

The release version of this Skill is recorded in the same directory's `skill.json`. The project's activation time, installed version, and latest check status are recorded in `.rankup/skill-state.json`.

Every time `rankup` is activated, locate the directory where the current `SKILL.md` resides and execute:

```bash
node "<rankup-skill-dir>/scripts/check-version.mjs" \
  --project-root . \
  --apply

undefined

- **Location**: `registry.md` in the Skill directory, next to `SKILL.md`, easily visible when in use (can be redirected with `RANKUP_REGISTRY_PATH`). It must write the project name and absolute path to be useful, so it is excluded by `rankup/.gitignore`, and `scripts/validate-rankup.mjs` **asserts that it must not be tracked by git**—`.gitignore` is only a convention, a `git add -f` can bypass it. The list is therefore exempt from project neutrality scanning, and the only basis for this exemption is that assertion.
- **Scan root directories**: From `--roots`, environment variable `RANKUP_PROJECT_ROOTS`, or `projectRoots` in `~/.rankup/config.json`. Never hardcode in the script.
- **Generated instead of manually written**: The entire table is rebuilt on each `scan`, always reading the current facts on disk. Manually maintained indexes will inevitably become outdated, which is a verified anti-pattern.
- **Read it on startup**: After this Skill is activated, if it finds that the current task requires a type of reusable operation, first check the list to see if another project has an existing solution, retrieve it from the corresponding path if available, do not rewrite.
- **Only index, do not copy**: The list does not move content. When using scripts from other projects, check the parameter conventions together; do not copy login states, property IDs, or account configurations across projects.
- **Signal feedback**: If a script is used by a second project, it means it is universal enough, consider refining the **method** into rules and feeding back to this Skill (still without any project information).

node "<rankup-skill-dir>/scripts/review.mjs" --project-root . --days 30

undefined

**`--new-only` is enabled by default.** The watermark is recorded by byte offset in `.rankup/review-state.json`: where the last review stopped, this time continues from there; only the new part is read for subsequent chats in the same session. Without it, the same conversations will be reread every time, which is a pure waste.

`--mark` is an **independent step, must be executed only after signals are truly extracted**. Do not set the watermark if it fails halfway or the output is truncated by budget, the same section will be reread next time—it is better to reread than to miss.

Covers Claude Code and Codex sessions for the current project, attributed by `cwd` in the records, worktrees and paths with spaces are recognized. Look for four types of content when reading condensed transcripts:

- **User's corrections**——The sentence after "No, it should be..." is usually a rule that should be preserved.
- **Verified conclusions**——Judgments with evidence; do not collect guesses without verification.
- **Pitfalls encountered and their root causes**——Especially those that took a long time to troubleshoot, write clear criteria to recognize them at a glance next time.
- **Facts that have overturned old records**——The corresponding entries in `.rankup/` must be **revised**, not written alongside.

On this basis, complete:

1. **Reconciliation**: Checkboxes in `plan.md` are lagging indicators, cross-verify with `git log`, route list, and online `sitemap.xml`; write back first if inconsistent before continuing.
2. **Filter signals**: Merge duplicates, delete outdated entries, revise falsified entries in `experience.md`——**Revise the original entry, do not keep conflicting conclusions side by side**. Delete unverified guesses directly.
3. **Refine feedback**: Rules that still hold after stripping site-specific information are fed back to the relevant reference files of this Skill. Evidence sources and numbers remain in the project's `experience.md`.
4. **Supplement scripts**: Are there any operations repeated a second time in this round but not solidified? Is the verified date in the script header expired, can it still run? Fix it if broken, do not bypass.
5. **Fill gaps**: Is `roadmap.md` outdated, is `iterations.md` missing failed rounds (failed rounds must clearly write the falsified hypothesis)?
6. **Refresh the list**: `node "<rankup-skill-dir>/scripts/registry.mjs" scan --roots <directory storing projects>`.
7. **Output**: A page of conclusions——what was fixed, what was deleted, what was fed back, the only improvement for the next round. Fix what can be fixed immediately, do not just list items.

pnpm dlx shadcn@latest init \
  --preset b1D0eCA4 \
  --template start \
  --monorepo \
  --rtl \
  --pointer

<rankup-skill-dir>/.env      # KEY=value, one per line; excluded by this repository's .gitignore