<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Commentary of Takao</title><link>https://takao.blog/en/tags/automation/</link><description>Recent content in Automation on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>OWASP ZAP in 2026: Advanced Scanning and CI/CD Integration</title><link>https://takao.blog/en/web/owasp-zap-advanced-2026/</link><pubDate>Tue, 09 Jun 2026 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/owasp-zap-advanced-2026/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post OWASP ZAP in 2026: Advanced Scanning and CI/CD Integration" /&gt;&lt;h2 id="beyond-basic-scanning"&gt;Beyond Basic Scanning
&lt;/h2&gt;&lt;p&gt;OWASP ZAP has evolved significantly since its early days. In 2026, it is no longer just a point-and-click proxy scanner — it is a full-featured security automation platform with a powerful API, a scriptable automation framework, and deep CI/CD integration. If you need the basics first, read our &lt;a class="link" href="https://takao.blog/web/owasp-zap/" &gt;OWASP ZAP installation and setup guide&lt;/a&gt;. This article covers advanced workflows for teams running security tests at scale.&lt;/p&gt;
&lt;h2 id="api-scanning-with-zap"&gt;API Scanning with ZAP
&lt;/h2&gt;&lt;p&gt;Modern applications rely heavily on REST and GraphQL APIs. ZAP&amp;rsquo;s OpenAPI and GraphQL support allows you to scan APIs without a browser.&lt;/p&gt;</description></item><item><title>Git Hooks for Automation: Beyond Code Quality</title><link>https://takao.blog/en/web/git-hooks-automation/</link><pubDate>Tue, 24 Dec 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/git-hooks-automation/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Git Hooks for Automation: Beyond Code Quality" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;Git hooks are executable scripts that run automatically at specific points in the Git lifecycle. While many developers associate them solely with code formatting and linting, their potential extends far beyond—into workflow automation, project management, and team collaboration. This article explores how to leverage Git hooks for comprehensive automation strategies.&lt;/p&gt;
&lt;h2 id="understanding-git-hooks"&gt;Understanding Git Hooks
&lt;/h2&gt;&lt;p&gt;Git hooks reside in the &lt;code&gt;.git/hooks/&lt;/code&gt; directory of every repository. They are standard executable scripts written in any language—bash, Python, Node.js, or Ruby. Hooks fall into two categories: &lt;strong&gt;client-side hooks&lt;/strong&gt; (pre-commit, pre-push, commit-msg) that run on a developer&amp;rsquo;s machine, and &lt;strong&gt;server-side hooks&lt;/strong&gt; (pre-receive, update, post-receive) that execute on the remote repository.&lt;/p&gt;</description></item><item><title>AI Content Generation Strategies for Developers in 2024</title><link>https://takao.blog/en/web/ai-content-generation/</link><pubDate>Tue, 29 Oct 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/ai-content-generation/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post AI Content Generation Strategies for Developers in 2024" /&gt;&lt;p&gt;AI content generation has moved from experimentation to production. Developers are no longer asking whether AI can generate content but how to integrate it reliably, at scale, and with quality control. This article provides a practical guide for building content systems with AI, focusing on technical architecture, quality assurance, and ethical deployment rather than prompt engineering tips.&lt;/p&gt;
&lt;h2 id="llm-powered-content-pipelines"&gt;LLM-Powered Content Pipelines
&lt;/h2&gt;&lt;p&gt;A well-architected AI content pipeline consists of several stages. It starts with content specification input including structured metadata, topic briefs, and tone guidelines. A prompt construction layer uses a template system with variable injection, guardrails, and few-shot examples. The LLM API dispatch routes requests to providers such as OpenAI, Anthropic, or open-source models via vLLM or Ollama. Post-processing handles format validation, content extraction, and cleanup before the result enters a human review queue.&lt;/p&gt;</description></item></channel></rss>