Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Show estimated review complexity on task card🧠

Open Beginner friendly
#609 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, react, tailwindcss
Domain
frontend

Research direction

Start with client/src/components/Board/TaskCard.jsx, the file named in the issue, and check how task snippets and the review status are rendered. Add the requested review complexity indicator based on snippet line counts; done when review tasks show the matching label and color, and tasks without snippets show no indicator. The issue says no backend changes are needed.

Written by the indexing model from the issue text.

Description

enhancement good first issue

🧠 Show estimated review complexity on task card

File: client/src/components/Board/TaskCard.jsx

Tasks in Review column have no complexity
indicator 💀 PR with 500 lines looks same
as 5 lines fr!!

Fix: calculate complexity score from snippets:
const getComplexity = (task) => {
if (!task.snippets?.length) return null
const totalLines = task.snippets.reduce(
(acc, s) => acc + s.code.split('\n').length, 0
)
if (totalLines < 20) return {
label: 'Quick review', color: 'text-green-400',
emoji: '⚡'
}
if (totalLines < 50) return {
label: 'Medium review', color: 'text-yellow-400',
emoji: '🔍'
}
return {
label: 'Deep review needed', color: 'text-red-400',
emoji: '🧠'
}
}

const complexity = getComplexity(task)

{task.status === 'review' && complexity && (
<span className={text-[10px] ${complexity.color}}>
{complexity.emoji} {complexity.label}

)}

~15 lines! No backend needed 🎯
Reviewers will LOVE this!! 🔥

Dominant language
JavaScript
Stars
39
Forks
105
Avg merge
1d 19h
Merged PRs (30d)
31

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anoopcodehack/DevBoard

All issues in anoopcodehack/DevBoard

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.