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

[epic] Fix It guidance: advice that is right for the résumé in front of the user

Closed
  • Is something wrong?
#1,086 1 comment 0 reactions 1 assignee View on GitHub

@Samhit21 is already working on this.

Since Sep 28, 2026.

Assessment

This issue has not been assessed yet.

Description

improvement ready-for-agent ux:score-clarity

Part of #811.

Owner: @Samhit21. This epic is a feature, not a ticket. The owner decides what "done" means for it, files what is missing, and gets each child implemented, mostly through Gaal.

Goal

Fix It (#810, landed in #1000) walks the user through what to change, one item at a time. It is only useful if every step it offers is right for the résumé in front of the user. Today several classes of résumé get advice that is wrong, and some signals the guidance depends on are miscounted or never recorded. This epic makes the guidance trustworthy across résumé shapes, and makes sure we can tell whether it is working.

Children

  • #1023: Fix It gives wrong advice for scanned PDFs, low-confidence contact, short summaries and multi-label Experience. These are the findings carried over from the closed PR #994.
  • #678: extractBulletsFromLines pools a marker-only line under an empty key, which inflates the Specificity denominator that the guidance reads from.
  • #1006: a feedback rating that is picked and then dismissed is never recorded. That is the signal that tells us whether Fix It helped.

The owner adds more children as they are found, and closes or splits any that turn out stale.

What owning it means

  1. Make each child Gaal-ready. Gaal reads only the issue body, never comments. So any decision the issue leaves open ("A or B", "decide, don't assume") goes into the body before the label does. #1023 and #1006 are both needs-clarification today, for exactly this reason.
  2. Label gaal in dependency order. A child is ready when it has one approach, touches no blocked paths (.github/, package.json, .claude/, CLAUDE.md, hook scripts), and fits in one PR. When in doubt, ask in the issue.
  3. Review and approve Gaal's PRs. Your approval is the merge gate. Check the diff against the child's acceptance criteria, not just CI. docs/reviewing-agent-prs.md covers what to look for.
  4. Flag the calls that are not yours alone. Some changes need a maintainer before they merge: anything that bumps ATS_SCORE_ALGO_VERSION (possible for #678) or changes an analytics event's shape (#1006). Tag @s-annam on those.
  5. Hand-write only what Gaal can't do, such as UX judgement or a blocked path.

Done when

  • Every child is closed, or explicitly deferred with a reason
  • Fix It gives no step on a scanned PDF that asks the user to add content already on the page
  • A dismissed rating is recorded
Dominant language
TypeScript
Stars
11
Forks
4
No merged PRs in 30d

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 offlinecv/OfflineCV

All issues in offlinecv/OfflineCV

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.