More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    File Backstory: Why This Code Is Like This

    1

    You get back its backstory from git: the changes that shaped it, what was undone, which commits wrote today's lines, and why, with every point citing its commit.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    File Backstory: Why This Code Is Like This

    File Backstory: Why This Code Is Like This

    Example session with this skill installed

    Why does the cash total round half-up when everything else rounds half-even? Look at src/pricing/rounding.py.

    • Read your context and instructions
    • Compiled the file backstory

    2025-04-08 · 4233f66 · Switch default rounding to half-even

    • Changed: DEFAULT_MODE becomes half-even and round_amount takes a mode (L18-L19, L34, L38).
    • Why (stated): "Half-up rounding gave invoice totals one cent above the ledger service on about 3% of March invoices." (4233f66)

    2025-04-09 · 979061e · fix

    • Changed: the cash step in invoice_total names half-up (L54). Before, it used the decimal context's default rounding, which is half-even.
    • Why (inferred): the message is only "fix". It came the day after 4233f66 made half-even the default for amounts, and it is the only line that names half-up, so a likely reading is that cash totals were meant to stay half-up. No message says so. (979061e, 4233f66)

    $ python3 scripts/story_check.py backstory/backstory.md --history backstory/history.json --log backstory/log.txt
    summary: 0 FIX, 0 ADVICE in backstory.md (15 entries; 17 reasons: 11 stated, 1 inferred, 5 unknown; 25 of 25 commits cited; 5 open questions). This checks citations (hashes, quotes, labels, line numbers), not whether the story is complete or the reading right: what git does not record is not in it.

    0 FIX, 0 ADVICE in backstory.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    English

    For developers who open a file and ask: why is this code like this?

    Point your agent at one file or folder. You get back its backstory from git: the changes that shaped it, what was undone, which commits wrote today's lines, and why, with every point citing its commit.

    What you get each run

    • backstory.md: five fixed sections: what the file does now (with line numbers), the changes that matter in date order, the changes that were undone, who wrote today's lines, and open questions.
    • backstory.html: the same as one printable page.
    • history.json: what the scan found, every fact with its short hash.

    Every reason is labelled

    • Stated: quoted word for word from the commit message, with the hash.
    • Inferred: a reading of the history, said plainly as a reading, citing the commits it rests on.
    • Unknown: git does not say. A message like "fix" or "wip" is never taken as a reason; it becomes an open question.

    Which change wrote these lines

    The agent exports the file's git log (followed across renames, with no email addresses) and its blame. A bundled Python script (standard library, read-only, no network calls, never runs git) reads those exports: commits, renames, reverts found from their messages, fixup and squash markers, ticket references, and each commit's share of today's lines.

    Checked, not just written

    A checker confirms every cited hash is in the export, every stated quote matches the commit message letter for letter, every reason has a label and every cited line exists. The agent fixes and checks again until no FIX is left.

    Honest about its limits

    It holds what git recorded. Tickets, pull request discussions and squashed history are not in the export, and the backstory says so. Revert detection reads commit messages, so a change undone by hand is found only by reading the history. The checker verifies citations, not whether the reading is right.

    One file, minutes

    File Backstory stays with one file or folder. For the decisions of a whole project across git, tickets, decision records and notes, use Decision Trail.

    Arabic

    The backstory can be written in Arabic with a right-to-left page. Quotes stay in the language of the commit message, and hashes and file names stay as they are.

    In the download: SKILL.md, the scripts, references (the backstory format, the git export commands for PowerShell and bash), and a complete example so you can see the output before you buy: a money-rounding module with 25 commits over a year (a rename, a revert, fixups, terse messages) and its English and Arabic backstories.

    بالعربي

    للمبرمجين الذين يفتحون ملفًا ويسألون: لماذا هذا الكود هكذا؟

    وجّه وكيلك إلى ملف أو مجلد واحد. تستلم قصته من git: التغييرات التي صنعته، وما أُلغي، والإيداعات التي كتبت أسطره الحالية، ولماذا، وكل نقطة معها رمز إيداعها.

    ماذا تستلم في كل مرة

    • ملف backstory.md: خمسة أقسام ثابتة: ماذا يفعل الملف الآن (مع أرقام الأسطر)، والتغييرات المهمة بترتيب التاريخ، والتغييرات التي أُلغيت، ومن كتب أسطر اليوم، وأسئلة مفتوحة.
    • صفحة backstory.html: الشيء نفسه كصفحة واحدة قابلة للطباعة.
    • ملف history.json: ما وجده الفحص، وكل معلومة مع رمز إيداعها.

    كل سبب له وصف

    • مذكور: منقول حرفيًا من رسالة الإيداع، مع رمزه.
    • مستنتج: قراءة للتاريخ، مكتوب بوضوح أنه قراءة، مع الإيداعات التي يستند إليها.
    • غير معروف: git لا يقول. رسالة مثل "fix" أو "wip" لا تُعتبر سببًا أبدًا، بل تصير سؤالًا مفتوحًا.

    أي تغيير كتب هذه الأسطر

    يصدّر الوكيل سجل git للملف (عبر تغييرات الاسم، وبلا عناوين بريد) وناتج blame. وسكربت بايثون مرفق (يقرأ فقط، بلا اتصال بالشبكة، ولا يشغّل git) يقرأ هذه الملفات: الإيداعات، وتغييرات الاسم، والإلغاءات من رسائلها، وعلامات fixup وsquash، وأرقام التذاكر، ونصيب كل إيداع من أسطر اليوم.

    مدقَّق، لا مكتوب فقط

    أداة فحص تتأكد أن كل رمز إيداع مذكور موجود في الملف المصدَّر، وكل اقتباس يطابق رسالة الإيداع حرفًا بحرف، ولكل سبب وصفه، وكل سطر مذكور موجود. يصلح الوكيل ويعيد الفحص حتى لا يبقى أي FIX.

    صادق في حدوده

    يحمل ما سجّله git فقط. التذاكر ونقاشات طلبات الدمج والتاريخ المضغوط ليست في الملف المصدَّر، والقصة تذكر ذلك. والأداة تتحقق من المصادر، لا من صحة القراءة.

    ملف واحد، في دقائق

    هذه المهارة لملف أو مجلد واحد. لقرارات مشروع كامل عبر git والتذاكر وسجلات القرار والمحاضر، استعمل Decision Trail.

    العربية

    تُكتب القصة بالعربي في صفحة من اليمين إلى اليسار. الاقتباسات تبقى بلغة رسالة الإيداع، ورموز الإيداع وأسماء الملفات كما هي.

    داخل الملف: ملف SKILL.md، والسكربتات، والمراجع، ومثال كامل لترى النتيجة قبل الشراء: وحدة تقريب مبالغ بـ25 إيداعًا خلال سنة، وقصتها بالإنجليزي والعربي.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    It holds what git recorded: tickets, pull request discussions and squashed history are not in the export, and the backstory says so. Revert detection reads commit messages, so a change undone by hand is found only by reading the history. One file or folder at a time; blame is for one to three files. The checker verifies citations (hashes, quotes, labels, line numbers), not whether the reading is right. backstory.html loads its fonts from Google Fonts when online and falls back to system fonts offline. يحمل ما سجّله git فقط، والأداة تتحقق من المصادر لا من صحة القراءة.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Software
    PythonGit

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    The agent runs read-only git commands (log and blame) and saves their output in a backstory folder; the bundled scripts (history_scan.py, story_check.py, make_page.py) read those files and write history.json, backstory.md and backstory.html. The scripts never run git, run nothing else and make no network calls. Author email addresses are left out of the exports. يشغّل الوكيل أوامر git للقراءة فقط، والسكربتات تقرأ الملفات المصدَّرة.

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    No. The agent runs only read-only git commands (log, blame, show) and saves their output; the scripts read those files and run nothing. لا، أوامر git للقراءة فقط.

    No. A stated reason is a quote the checker matches against the commit message. A reading is labelled inferred, and a terse message such as "fix" makes the reason unknown. لا، السبب المذكور اقتباس تتحقق منه أداة الفحص.

    File Backstory answers for one file or folder from git alone, in minutes, and says which commit wrote today's lines. Decision Trail reconstructs a whole project's decisions from git, tickets, decision records and notes. هذه لملف واحد من git، وتلك لقرارات المشروع كله.

    No. The export commands leave them out, and the checker fails a backstory that contains one. لا، أوامر التصدير تستبعدها.

    It finds reverts from their commit messages. A change undone by hand is found only when the agent reads the history, and the backstory says how it was found. يجد الإلغاءات من رسائلها، وما أُلغي يدويًا يجده الوكيل بقراءة التاريخ.

    Yes. The export commands are given for PowerShell and for bash, and the files stay UTF-8. نعم، الأوامر مكتوبة لـ PowerShell وbash.

    Yes, as an added option: a right-to-left page. Quotes stay in the language of the commit message. نعم، والاقتباسات تبقى بلغة رسالة الإيداع.

    New in Code Quality & Review