بنقرة واحدة
solve-issue-local
Repo-specific instructions to use alongside the global solve-issue skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Repo-specific instructions to use alongside the global solve-issue skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Pull the next recipe(s) from the pipeline snapshot audit queue, cross-reference each against its cached source HTML, and file issues for any real conversion bugs. Use for a spot-check of extraction/parsing quality, or after changing extraction code to hunt for regressions.
Bring up the local Ramekin dev server, drive the UI with playwright-cli, and capture screenshots/snapshots for any kind of UI audit (design critique, bug repro, UX review, regression check).
Repo-specific instructions to use alongside the global create-pr skill.
Analyze the density gap report to find the highest-impact ingredients missing density data, filtering out intentionally-null entries and existing aliases. Use when deciding which ingredient to add next.
Pick one high-impact ingredient from the density gap report, find a reliable density, and add it to the system. Use when adding ingredient density data.
| name | solve-issue-local |
| description | Repo-specific instructions to use alongside the global solve-issue skill. |
Use these notes together with the global solve-issue skill.
Makefile first and use existing make targets instead of invoking docker or cargo directly.make test and make lint.make pipeline and spot-check the resulting diff for regressions.make setup-claude-web is safe to run anywhere and is already covered by make check-deps.issues/ as pN-*.json5 or blocked-*.json5; see doc/issues.md.