Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Add a Cron Expression Explainer tool

オープン
  • 何か問題がありますか？
#86 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
58/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
nextjs, tailwindcss, typescript
領域
developer-experience, frontend

調査の方向性

Read lib/tools.ts and its Tool interface, then inspect the complete example in app/(tools)/base64/ and the Add a tool section of the README. Implement the pure cron logic in lib/cron.ts with tests in lib/__tests__/cron.test.ts, then add the registry entry and route, client, and Open Graph image. Done means the listed acceptance tests, scoped UI, checklist, and lint, test, and build commands all pass.

索引モデルが issue の本文から書いたものです。

説明

enhancement hacktoberfest help wanted new tool

Paste a crontab line and get a plain-English description plus the next run times. It's useful any time you touch CI schedules, Kubernetes CronJobs or GitHub Actions.

Route: /cron-explainer

Suggested registry values: title Cron Expression Explainer, tagline Scheduling, heroHeading Cron Expression Explainer with heroDim "", features ["Plain English", "Next runs", "Ranges and steps", "Macros", "UTC or local"].

Core logic in lib/cron.ts (no new dependency, please)

  • parseCron(expr) for standard 5-field cron (minute, hour, day of month, month, day of week) with *, lists, ranges, steps (*/15, 1-10/2), names (JAN, MON) and macros (@hourly, @daily, @weekly, @monthly, @yearly). Errors name the field that failed.
  • describeCron(parsed) returning an English sentence
  • nextRuns(parsed, from: Date, count, { utc }) returning Date[]. Follow the classic rule that when both day of month and day of week are restricted, a time matches if either one matches. Cap the search horizon so an impossible schedule like 0 0 31 2 * returns an empty list with a message instead of looping.

v1 scope: the input, the description, a field-by-field breakdown table, the next 5 runs with a UTC / local toggle, and a few preset chips.

Out of scope for v1: seconds and year fields (Quartz style), Jenkins H syntax, a timezone picker.

Where to look

  • lib/tools.ts (the registry and the Tool interface)
  • app/(tools)/base64/ (a complete tool to copy the structure from)
  • The "Add a tool" section of the README

Acceptance criteria

  • Tests: */15 * * * * is described as every 15 minutes, 0 9 * * 1-5 as weekdays at 09:00, nextRuns from a fixed UTC date, the day-of-month or day-of-week rule (0 0 1 * 1), 0 0 31 2 * returns no runs, and 60 * * * * errors and mentions the minute field
  • UI as scoped above
  • The standard new-tool checklist below is complete

Standard new-tool checklist

Everything (home grid, metadata, JSON-LD, OG image, sitemap, manifest, command palette) is driven by the registry in lib/tools.ts, so a new tool is mostly one registry entry plus a route.

  • Add an entry to TOOLS in lib/tools.ts filling every field of the Tool interface (lib/tools.ts:19-52). Use applicationCategory: "DeveloperApplication", reuse the CTA_PROJECTS / CTA_CONTACT constants for the CTA links, and set sitemapPriority: 0.9 like the other tools.
  • Pick accentVar from the accent variables in app/globals.css (the list is under "Adding a tool" in CONTRIBUTING.md). Take one that no tool uses yet, or the one the fewest tools have if they're all taken. Don't use --rose, it's the color of error messages. Set accentHex to that variable's dark-theme value. heroDim must be "" or a substring of heroHeading.
  • Write 3 or 4 FAQs (3 renders as a 3-column grid, see components/shared/ToolPageLayout.tsx:25). Keep metaTitle under 60 characters and metaDescription around 150 to 160.
  • Keep features and ogDescription to plain Latin text and punctuation. The social card font is a subset with no arrow or symbol glyphs (lib/og.tsx:33-36).
  • Create app/(tools)/<slug>/page.tsx, <Name>Client.tsx (with "use client"), and opengraph-image.tsx. Copy page.tsx and opengraph-image.tsx from app/(tools)/base64/ and change the slug.
  • Put all pure logic in lib/<name>.ts (no React, no DOM) with tests in lib/__tests__/<name>.test.ts. Tests can import with @/ like the app does (vitest.config.ts has the alias).
  • Nothing leaves the browser: no network calls with user input, no analytics, no third-party scripts (the CSP in middleware.ts blocks external scripts anyway).
  • Reuse shared pieces: CopyButton, useToast, and optionally useRegisterCommands for command palette actions (example in app/(tools)/base64/Base64Client.tsx:43-53).
  • Every input has a visible label or an aria-label, the tool works with the keyboard alone, and it looks right in both light and dark themes.
  • Add the tool to the "Which tool?" dropdown in .github/ISSUE_TEMPLATE/bug_report.yml.
  • npm run lint && npm run test && npm run build passes.

One new tool per contributor, so more people get a chance. Add your registry entry at the end of TOOLS and rebase on develop before asking for review, since other new tools will touch the same file.

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off develop, and open your PR against develop with Closes #86 in the description.

主要言語
TypeScript
スター
1
フォーク
9
平均マージ
9時間 50分
マージ済み PR（30日）
105

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

codercops/toolbelt のほかの issue

codercops/toolbelt の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。