القائمة
Pattern for closing issues where the deliverable is documented blockers rather than feature completion
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/vamseeachanta/workspace-hub --skill blocker-reporting-outcome-validationيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | blocker-reporting-outcome-validation |
| description | Pattern for closing issues where the deliverable is documented blockers rather than feature completion |
| version | 1.0.0 |
| source | auto-extracted |
| extracted | "2026-04-13T00:00:00.000Z" |
| metadata | {"tags":["issue-closure","validation","blocker-documentation"]} |
When an issue's acceptance criteria include explicit blocker documentation rather than feature completion: (1) Run existing test suite to validate ledger/index backing and content hashes; (2) Generate a blocker-reporting artifact (e.g., YAML handoff) that lists each target with its blocker reason; (3) Verify all targets have either valid summaries OR documented blockers; (4) Cross-reference artifact paths in handoff comments to #2227 or next-phase issue; (5) Close the issue with acceptance criteria met via blocker documentation, not feature delivery.