<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>PyPI recent updates for codestory-cli</title>
    <link>https://pypi.org/project/codestory-cli/</link>
    <description>Recent updates to the Python Package Index for codestory-cli</description>
    <language>en</language>    <item>
      <title>0.2.2</title>
      <link>https://pypi.org/project/codestory-cli/0.2.2/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Thu, 19 Feb 2026 12:09:59 GMT</pubDate>
    </item>    <item>
      <title>0.2.1</title>
      <link>https://pypi.org/project/codestory-cli/0.2.1/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Fri, 23 Jan 2026 13:16:29 GMT</pubDate>
    </item>    <item>
      <title>0.2.0</title>
      <link>https://pypi.org/project/codestory-cli/0.2.0/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Fri, 23 Jan 2026 11:40:23 GMT</pubDate>
    </item>    <item>
      <title>0.1.13</title>
      <link>https://pypi.org/project/codestory-cli/0.1.13/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Thu, 22 Jan 2026 01:42:39 GMT</pubDate>
    </item>    <item>
      <title>0.1.12</title>
      <link>https://pypi.org/project/codestory-cli/0.1.12/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Sat, 10 Jan 2026 08:54:18 GMT</pubDate>
    </item>    <item>
      <title>0.1.11</title>
      <link>https://pypi.org/project/codestory-cli/0.1.11/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Wed, 07 Jan 2026 10:43:28 GMT</pubDate>
    </item>    <item>
      <title>0.1.10</title>
      <link>https://pypi.org/project/codestory-cli/0.1.10/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Wed, 07 Jan 2026 10:19:42 GMT</pubDate>
    </item>    <item>
      <title>0.1.9</title>
      <link>https://pypi.org/project/codestory-cli/0.1.9/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Mon, 05 Jan 2026 12:12:55 GMT</pubDate>
    </item>    <item>
      <title>0.1.8</title>
      <link>https://pypi.org/project/codestory-cli/0.1.8/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Mon, 05 Jan 2026 10:10:58 GMT</pubDate>
    </item>    <item>
      <title>0.1.7</title>
      <link>https://pypi.org/project/codestory-cli/0.1.7/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Mon, 05 Jan 2026 07:55:14 GMT</pubDate>
    </item>    <item>
      <title>0.1.6</title>
      <link>https://pypi.org/project/codestory-cli/0.1.6/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Sat, 03 Jan 2026 11:04:15 GMT</pubDate>
    </item>    <item>
      <title>0.1.5</title>
      <link>https://pypi.org/project/codestory-cli/0.1.5/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Sat, 03 Jan 2026 05:48:15 GMT</pubDate>
    </item>    <item>
      <title>0.1.4</title>
      <link>https://pypi.org/project/codestory-cli/0.1.4/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Thu, 01 Jan 2026 17:26:50 GMT</pubDate>
    </item>    <item>
      <title>0.1.3</title>
      <link>https://pypi.org/project/codestory-cli/0.1.3/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Mon, 22 Dec 2025 14:04:35 GMT</pubDate>
    </item>    <item>
      <title>0.1.2</title>
      <link>https://pypi.org/project/codestory-cli/0.1.2/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Sat, 20 Dec 2025 12:51:56 GMT</pubDate>
    </item>    <item>
      <title>0.1.1</title>
      <link>https://pypi.org/project/codestory-cli/0.1.1/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Fri, 19 Dec 2025 05:51:00 GMT</pubDate>
    </item>    <item>
      <title>0.1.0</title>
      <link>https://pypi.org/project/codestory-cli/0.1.0/</link>
      <description>Every project should have a good story behind it. With a good story (git history), you can reason about changes in a way that would be impossible just looking at a codebase. But let us do the work in creating that story</description>
<author>ademfcan@gmail.com</author>      <pubDate>Fri, 19 Dec 2025 04:03:02 GMT</pubDate>
    </item>    <item>
      <title>0.0.1</title>
      <link>https://pypi.org/project/codestory-cli/0.0.1/</link>
      <description>An AI-powered abstraction layer above Git. Focus on vibecoding, let codestory handle the rest.</description>
<author>ademfcan@gmail.com</author>      <pubDate>Thu, 04 Dec 2025 13:05:28 GMT</pubDate>
    </item>  </channel>
</rss>