<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>My notes and stuff - Claude Code</title>
    <subtitle>This is just a space for me to share some notes and thoughts. I hope someone finds something useful here.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://suchaboris.com/tags/claude-code/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://suchaboris.com/"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-06-10T00:00:00+00:00</updated>
    <id>https://suchaboris.com/tags/claude-code/atom.xml</id>
    <entry xml:lang="en">
        <title>daily summary ai skill</title>
        <published>2026-06-10T00:00:00+00:00</published>
        <updated>2026-06-10T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://suchaboris.com/blog/daily-summary-ai-skill/"/>
        <id>https://suchaboris.com/blog/daily-summary-ai-skill/</id>
        
        <content type="html" xml:base="https://suchaboris.com/blog/daily-summary-ai-skill/">&lt;p&gt;For years I&#x27;ve been writing down what I worked on each day. Partly to look back and remember things, partly as a running record for performance reviews or when someone asks &quot;how did you do that thing six months ago?&quot; It works for both work and personal projects.&lt;&#x2F;p&gt;
&lt;p&gt;The problem is that I don&#x27;t actually enjoy the writing part. I&#x27;d sometimes do it mid-day, sometimes in the evening trying to reconstruct what I&#x27;d done, sometimes the next morning looking back at the day before. The most valuable part is always the looking back, not the writing itself.&lt;&#x2F;p&gt;
&lt;p&gt;So I started using AI for this. I created a Claude Code skill that runs at the end of the day and automatically collects what I&#x27;ve done: coding agent logs, GitHub activity, Jira issues assigned to me, Slack threads I participated in, and my calendar. From all of that it generates a concise summary with embedded links, which then gets written directly into my journal.&lt;&#x2F;p&gt;
&lt;p&gt;The part I find most useful is that it also posts comments back to the relevant Jira tickets. That means my teammates can see what happened on a ticket without me writing it up separately, and six months later I can look at any ticket and see exactly what was done and why.&lt;&#x2F;p&gt;
&lt;p&gt;For personal projects the setup is simpler, just coding logs without the work integrations, but it&#x27;s still useful.&lt;&#x2F;p&gt;
&lt;p&gt;I&#x27;m not sharing the exact skill text because I think the point is for each person to customize it for what matters to them, not copy what matters to me. But if you have a habit of writing things down, or want to build one with the goal of being able to recall how something was done or why a decision was made, this kind of skill makes the entry into that workflow almost effortless.&lt;&#x2F;p&gt;
</content>
        
    </entry>
</feed>
