تشغيل أي مهارة في Manus بنقرة واحدة

doc-test-alignment

النجوم٣

التفرعات١

آخر تحديث٢٢ يونيو ٢٠٢٦ في ١٨:٥٨

Verify that committed docs (README.md, CLAUDE.md, SKILL.md descriptions) still describe what the code and tests actually do. Use at the end of a plan, before PR creation, or when the user says "check doc-test alignment", "verify docs", or "do the docs still match the code". STUB — `scripts/check.sh` exits with a not-yet-implemented error today; the contract for what it will do lives in this file.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

agentculture

agentculture/lobes-cli

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name

doc-test-alignment

description

doc-test-alignment (stub)

Vendored from steward (canonical upstream: docs/skill-sources.md); this copy is owned by lobes and may diverge.

This skill is a stub. The real workflow is intentionally not yet implemented — the file exists so that steward verify can find it and so contributors who land here know it is on the roadmap, not forgotten.

How to run

scripts/check.sh is the entry point. Today it prints a not-yet-implemented notice and exits non-zero. When the workflow lands, the script will gate PR-readiness on the alignment contract below; until then, treat any green exit code from this script as a bug.

What it will check

The skill is the contract for four narrow alignments. README.md command examples must still execute against the current checkout and produce output that matches the surrounding prose. The "build/test/publish" command lines in CLAUDE.md must do the same. For each .claude/skills/<name>/, the SKILL.md description frontmatter must agree with what the scripts under scripts/ actually do — surfacing disagreements (e.g. SKILL.md claims the skill bumps versions but scripts/ has no bump script). And for each test, the test name should still describe the assertions the test makes — flagging drift where the name advertises a feature the assertions no longer touch.

Why it ships as a stub

Each of those four checks is independently non-trivial. Shipping a partial implementation would either silently pass when it shouldn't, or false-positive on intentional doc-vs-code differences. The right path is to land the checks one at a time, with their own tests, behind a steward verify --check doc-test-alignment flag. The parent verbs (verify, doctor) are named in the "Roadmap" section of CLAUDE.md; the broader sibling-pattern contract lives in docs/sibling-pattern.md.

What this stub guarantees today

The skill directory exists, so steward verify's skills-convention check finds the standard layout (SKILL.md + scripts/ with an entry-point).
scripts/check.sh is the entry-point script, satisfying the steward skills convention requirement that every skill ships an executable script.
This SKILL.md is the contract for what the skill will do — when the implementation lands, it must satisfy this description or the description must move first.

المزيد من هذا المستودع

نفس المستودع

recall

agentculture/lobes-cli

Search the shared eidetic memory store and get back ranked, provenanced records. Drives `eidetic recall` with four search modes — exact (verbatim substring), approximate (vector/semantic), keyword (BM25 lexical), and hybrid (a weighted blend of vector+keyword, the default) — each hit carrying its text, full metadata, a relevance `score`, and a freshness `signal`. Recall passively reinforces matched records (bumps last_recall + recall_count). Shadowed and archived records are excluded by default; use --include-shadowed / --include-archived to retrieve them. The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree); the wrapper defaults queries to this agent's PERSONAL, PRIVATE scope (`--scope lobes --visibility private`, suffix read from culture.yaml) — matching where /remember writes — so a no-flag recall returns this agent's own private records plus the shared public pool, and Claude and the colleague backend recall each other's memories because both resolve the same suffix via this ski

2026-06-263

remember

agentculture/lobes-cli

Ingest records into the shared eidetic memory store so they can be recalled later. Drives `eidetic remember`: accepts one record as a JSON object, or a batch as NDJSON on stdin for bulk ingest. Upsert is idempotent by id (and dedups by content hash) — re-remembering updates in place, never duplicates. Stamps a `created` date on every record at ingest time. Accepts `supersedes` (id of the record this one replaces, for within-scope shadowing via `sweep`) and `links` (list of related-memory ids). The store lives at ~/.eidetic/memory (a home-dir path outside any git worktree), and the wrapper defaults records to this agent's PERSONAL, PRIVATE scope (`--scope lobes --visibility private`, suffix read from culture.yaml) so they don't leak to a default/other-scope recall — Claude and the colleague backend still share them because both resolve the same suffix via this skill. Pass `--visibility public` to contribute to the shared public pool instead. Use when the user says "remember this", "store this", "save to memory

2026-06-263

ask-colleague

agentculture/lobes-cli

Ask colleague — a *different* backend/model than you (e.g. a local vLLM Qwen) — to take a scoped repo task off your plate, then fold its answer back. The point isn't a stronger model; it's a second, independent mind, and that diversity is the value: `ask-colleague review` gets a candid second opinion on a diff, `ask-colleague explore` gets a fresh read of an area, `ask-colleague write` hands off a small implementation, `ask-colleague feedback` grades a finished work item (the ROI loop), and `ask-colleague clean` reaps stale/corrupt `colleague/*` branches a crashed run left behind (which can break `git fetch`). Pilot a running work item with `monitor`/`guide`/`stop`. Reach for it REFLEXIVELY, the way you'd lean over to the teammate at the next desk — not only when asked: before you present or open a PR on a non-trivial committed diff, run `review` for a diverse second opinion; for a fresh read of an unfamiliar area whose answer is independent of your current context, run `explore`. Both are read-only — isolate

2026-06-223

cicd

agentculture/lobes-cli

Steward's CI/CD lane, layered on `agex pr`. Delegates lint / open / read / reply / delta to agex; adds two steward extensions — `status` (SonarCloud quality gate + hotspots + unresolved-thread tally) and `await` (read --wait + status with non-zero exit on Sonar ERROR or unresolved threads). Use when: creating PRs in steward, handling review feedback, polling CI status, or the user says "create PR", "review comments", "address feedback", "resolve threads". Renamed from `pr-review` in steward 0.7.0; rebased on agex in 0.12.0.

2026-06-223

communicate

agentculture/lobes-cli

Cross-repo + mesh communication from steward: file tracked GitHub issues on sibling repos, fetch issues from sibling repos to inline current state into briefs, and send live messages to Culture mesh channels. Use when the next step lives outside steward (a brief for a sibling-repo agent, a status ping for a Culture channel, or pulling an issue body + comments into context). Issue posts auto-sign with `- steward (Claude)`; mesh messages are unsigned (the IRC nick is the speaker). Not for in-steward issues — use `gh issue create` or the `cicd` skill for those. Renamed from `coordinate` in steward 0.8.0; absorbed `gh-issues` in 0.9.1. Issue I/O is backed by `agtag` (>=0.1) starting in 0.11.0.

2026-06-223

model-runner

agentculture/lobes-cli

Run, assess, and switch the local vLLM model via the `lobes` CLI (lobes-cli). Use when changing the served model, starting/stopping the server, load-testing a candidate (e.g. an NVFP4 checkpoint), or producing the numbers for a per-model doc under docs/.

2026-06-223

name

doc-test-alignment

description

doc-test-alignment (stub)

Vendored from steward (canonical upstream: docs/skill-sources.md); this copy is owned by lobes and may diverge.

How to run

What it will check

Why it ships as a stub

What this stub guarantees today

The skill directory exists, so steward verify's skills-convention check finds the standard layout (SKILL.md + scripts/ with an entry-point).
scripts/check.sh is the entry-point script, satisfying the steward skills convention requirement that every skill ships an executable script.
This SKILL.md is the contract for what the skill will do — when the implementation lands, it must satisfy this description or the description must move first.