القائمة
Fix Biome linting/formatting errors in 1-3 files using auto-fix and minimal manual edits. Use proactively for lint issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | fix-lint |
| description | Fix Biome linting/formatting errors in 1-3 files using auto-fix and minimal manual edits. Use proactively for lint issues. |
| disable-model-invocation | false |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
| model | haiku |
| tier | 1 |
| intent | fix |
| max-files | 3 |
| max-loc | 100 |
Fix Biome linting and formatting errors in specified files: run pnpm run biome:fix (or equivalent), then resolve any remaining issues with minimal manual edits. Adapted for this repo: Astro, TypeScript, Biome; no logic changes; follow AGENTS.md conventions.
Tier: 1 - Light/Cheap
Reasoning: Mechanical fixes (formatting, rule compliance); small scope (1–3 files, <100 LOC); low risk.
$FILES: File(s) to fix (paths or "current file"); optional — default to files reported by Biome$RULES: Specific rules to focus on (default: all reported)Before running this skill, ensure:
pnpm run biome:fix
# or for specific files:
pnpm exec biome check --write "path/to/files"
pnpm run biome:check
pnpm run astro:check
## ✅ Lint Fix Complete
### Files
- `{file1}`: {what was fixed}
- `{file2}`: {what was fixed}
### Validation
- pnpm run biome:check: ✅
- pnpm run astro:check: ✅
### Commit Message
style: fix Biome issues in {files}
## ❌ Fix Lint Not Enough
### Reason
{Remaining issues require type changes / refactor / many files}
### Recommendation
Escalate to Tier 2 or use quick-fix for logical issues.
Stop and escalate if:
pnpm run biome:check passes for modified filespnpm run astro:check passesCreate blog posts — from a topic (writes content) or with provided content (scaffolding). Use proactively when creating new blog posts or articles.
Pre-publication audit for blog posts — comprehensive final review of SEO, AEO, accessibility, images, content quality, i18n parity, and project conventions before publishing. Use proactively before publishing any blog post.
Pre-publication audit for blog series — validates series definition, post ordering, cross-post consistency, navigation, and runs individual post audits for all posts in the series. Use proactively before publishing any blog series.
Audit the blog tag taxonomy — frequency analysis, orphan detection, hierarchy validation, and proposals for new subtopic tags. Read-only — proposes, never modifies tags or posts. Use proactively before each release cycle or after a content drop of 5+ posts.
Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill (DailybotHQ/agent-skill) and/or the Dailybot CLI (DailybotHQ/cli), wiring the plan lifecycle into best-effort agent updates - kickoff when a plan starts, significant task completions, a blocked report when an unattended run halts, and a milestone on plan completion - with payloads derived from the plan's state layer, and optionally committing the Dailybot skill's deterministic hook enforcement (dailybot hook lifecycle hooks, CLI >= 1.12.0) so the agent harness itself reminds agents about unreported work. Opt-in, never required, never blocks the work, reconciles existing setups instead of clobbering them, and defers all auth to the Dailybot skill's own consent flow. Use when the developer or team already uses Dailybot and wants DWP progress visible to humans.
Optional DeepWorkPlan addon that safely upgrades a repo's dependencies — reasoning about the repo's ACTUAL package manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer, and more) rather than assuming npm — with a batched, validated, revertible workflow that detects the manager and manifests/lockfiles, classifies upgrades (patch/minor/major), upgrades in safe batches, runs the repo's real validation gate after each batch, reverts a failing batch, and summarizes. Opt-in, never required, reconciles with the repo's existing tooling. Use when the developer wants to bring dependencies up to date without breaking the build.